It seems like you're exploring different approaches to enhance PageElement's search methods to include the element itself along with its siblings and descendants. Option #2, adding new generator properties like self_and_next_elements and self_and_next_siblings, alongside the existing self_and_descendants and self_and_parents, appears to be a pragmatic choice. This method could leverage the PageElement.filter() method effectively for comprehensive searches. Deprecating 'include_self' in favor of 'consider_self' reflects a thoughtful evolution in method naming, maintaining backward compatibility while aligning with your refined approach.
www.gbpro.pro
It seems like you're exploring different approaches to enhance PageElement's search methods to include the element itself along with its siblings and descendants. Option #2, adding new generator properties like self_and_ next_elements and self_and_ next_siblings, alongside the existing self_and_ descendants and self_and_parents, appears to be a pragmatic choice. This method could leverage the PageElement. filter( ) method effectively for comprehensive searches. Deprecating 'include_self' in favor of 'consider_self' reflects a thoughtful evolution in method naming, maintaining backward compatibility while aligning with your refined approach.
www.gbpro.pro