Open
Conversation
There was a problem hiding this comment.
Performed full review of fe02e69...686514f
13 files reviewed | 0 comments | Review on Mesa | Edit Reviewer Settings
There was a problem hiding this comment.
Performed full review of fe02e69...686514f
13 files reviewed | 0 comments | Review on Mesa | Edit Reviewer Settings
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.
/inputroutesTL;DR
Extended the server with a new, dedicated set of
/inputAPI routes for programmatic control over mouse, keyboard, and window interactions.Why we made these changes
To introduce comprehensive remote control and automation capabilities by providing a specialized API for interacting with the desktop environment's input devices and windows. This refactors the server to focus specifically on these functionalities.
What changed?
/input/mouse/*,/input/keyboard/*,/input/window/*, and/input/display/*routes for mouse movement, clicks, keyboard typing, key presses, and extensive window management (activate, focus, move, resize, close, query information).main.goto transform the general API server into a dedicated 'input API' server, removing previous OpenAPI specification serving and FFmpeg dependencies.input.go,input_api.go,input_handlers.go,router.go,main_input.go) to define data structures, implement API logic, set up HTTP handlers (often leveragingxdotool), and configure the new server's entry point.server/README.mdwith detailed examples andcurlcommands for all new/inputendpoints.input_test.gowith unit tests for various input handlers./healthendpoint to report service status and uptime.Description generated by Mesa. Update settings