Skip to content

Conversation

straker
Copy link
Contributor

@straker straker commented Jul 31, 2025

Closes: #4845

@straker straker marked this pull request as ready for review July 31, 2025 18:03
@straker straker requested a review from a team as a code owner July 31, 2025 18:03
dbjorge
dbjorge previously approved these changes Aug 7, 2025
Copy link
Contributor

@dbjorge dbjorge left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks right to me (modulo a nit about improving the tests that you can choose whether to prioritize or not), but asked @WilcoFiers to double check my thinking on the implementation change.

I could see an argument that this should be treated as a breaking change, but I think I'd probably lean towards treating it as a bugfix.

WilcoFiers
WilcoFiers previously approved these changes Aug 7, 2025
Copy link
Contributor

@WilcoFiers WilcoFiers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is potentially disruptive to deduplication algorithms. While this is a bug fix, I don't think we should release this as a patch. We may want to prioritize a 4.11 release for this.

@straker straker dismissed stale reviews from WilcoFiers and dbjorge via 0fa8c3f August 7, 2025 19:11
@straker straker changed the title fix(get-xpath): return proper relative selector for id feat(get-xpath): return proper relative selector for id Aug 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Relative path xpath using id does not use //
4 participants