fix: handle comma-separated coordinates in move_mouse tool#262
Merged
Conversation
mlikasam-askui
requested changes
Apr 10, 2026
programminx-askui
requested changes
Apr 10, 2026
Contributor
Author
|
@programminx-askui @mlikasam-askui : I addressed the comments of you both in my last commit |
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
3 participants
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.
The agent quite often passes both x/y coordinates as a single comma-separated string to the
xparameter (e.g.,x="330, 182"orx="54, "), causing theint()conversion to fail.I added parsing the comma-separated string and extract both coordinates before converting to int to make it more robust