fix: targeted extract not allowing xpath=

[seanmcguire12]

why

• we were passing the wrong variable to getAccessibilityTree which broke targeted extract for selectors with the xpath= prefix

what changed

• pass the parsed xpath instead of the raw selector

test plan

• targeted extract evals

[changeset-bot]

🦋 Changeset detected

Latest commit: e1a8d98

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[greptile-apps]

Greptile Summary

This PR fixes a critical bug in the targeted extract functionality where XPath selectors were not working correctly. The issue was caused by passing the raw selector string (including the xpath= prefix) to getAccessibilityTree instead of the parsed XPath expression. The fix is a simple but important change that properly strips the xpath= prefix before passing the selector to the tree generation function.

This change is important for maintaining the library's XPath-based extraction capabilities, which are documented in the changelog as being introduced in version 1.14.0. The fix ensures that users can continue to use XPath selectors for targeted extraction as intended.

Confidence score: 5/5

1. This PR is extremely safe to merge
2. The change is minimal, well-isolated, and fixes a clear bug with an obvious solution
3. No files need special attention - the change is straightforward and well-tested

_{1 file reviewed, no comments
Edit PR Review Bot Settings | Greptile}