feat: Add coordinate-based APIs for gesture calls #843
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions bot
pushed a commit
that referenced
this pull request
Jan 31, 2024
## [6.0.0](v5.15.8...v6.0.0) (2024-01-31) ### ⚠ BREAKING CHANGES * The /wda/tap/:uuid endpoint has been replaced by /wda/element/:uuid/tap and /wda/tap ones ### Features * Add coordinate-based APIs for gesture calls ([#843](#843)) ([feda373](feda373))
|
🎉 This PR is included in version 6.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This was referenced Jan 31, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
BREAKING CHANGE: The
/wda/tap/:uuidendpoint has been replaced by/wda/element/:uuid/tapand/wda/taponesCurrently the way these APIs are called from xcuitest is suboptimal as we have to lookup for the application object every time they are called without elementId, which creates unnecessary overhead and is potentially error-prone (see appium/appium#19739)
The change ensures WDA assigns activeApplication instance itself without making other unnecessary calls.
After this change is published it is necessary to update xcuitest driver to use the new API endpoints for cases where elementId is unset