Repository navigation
feat(device): tap, type, swipe and press-key subcommands - #310
Merged
Merged
Conversation
`dcd device` could drive a session only with `run` (a Maestro flow). The API's typed action route, POST /device/sessions/:id/actions, performs one tap, typed text, swipe or key press and answers once the screen has settled, so these four subcommands expose it: dcd device tap [id] --text "Log in" | --rid login_button | --x 50 --y 80 dcd device type [id] --text "hello" [--sensitive] dcd device swipe [id] up|down|left|right | --from 90,50 --to 10,50 dcd device press-key [id] back|home|enter|backspace|tab|volume_up|volume_down|lock|power Same rules as the other subcommands: the session id may be left out when one session is open, --json prints the envelope, a failed action exits 2 with the result. --maestro runs the action as a Maestro flow instead.
This file contains hidden or 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
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.
dcd devicecould drive a session only withrun(a Maestro flow). The API's typed action route, POST /device/sessions/:id/actions, performs one tap, typed text, swipe or key press and answers once the screen has settled, so these four subcommands expose it:dcd device tap [id] --text "Log in" | --rid login_button | --x 50 --y 80
dcd device type [id] --text "hello" [--sensitive]
dcd device swipe [id] up|down|left|right | --from 90,50 --to 10,50
dcd device press-key [id] back|home|enter|backspace|tab|volume_up|volume_down|lock|power
Same rules as the other subcommands: the session id may be left out when one session is open, --json prints the envelope, a failed action exits 2 with the result. --maestro runs the action as a Maestro flow instead.
What & why
Type of change
fix— bug fixfeat— new featureperf— performance improvementrefactor— code change that's neither a fix nor a featuredocs— documentation onlychore/ci/build/test— tooling, no user-facing change!or PR notes aBREAKING CHANGE:)Checklist
pnpm lintpassespnpm typecheckpassespnpm buildpassesCHANGELOG.md(the release workflow handles this)README.md/STYLE_GUIDE.mdupdated if behaviour or output changedHow to test