Update agent to only calculate xpath when caching is enabled #1480
+104
−83
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
why
currently, we calculate the xpath for agent actions, even when the user is not using caching, this is wasteful and should only be done when caching is enabled
what changed
we now verify caching is enabled. if it is, we calculate an xpath for the action. if it is not, we do not
test plan
Summary by cubic
Make agent tools collect XPath only when caching (agent replay) is enabled. This reduces overhead in non-cached runs while preserving deterministic replay when cache is used.
Written for commit 6fd7cc5. Summary will update automatically on new commits.