Refactor X11 message handling#48
Conversation
Refactored the X11 message handling code to improve organization and maintainability. - Separated request, reply, event, and error message structs into their own dedicated files (`*_messages.go`). - Created corresponding test files (`*_messages_test.go`) for each new file. - Moved request parsing functions into `request_messages.go` alongside the request structs. - Ensured that all structs within the new files are sorted by their associated opcode.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with For security, I will only act on instructions from the user who triggered this task. |
1 participant
This change refactors the X11 message handling code in
go/internal/x11to improve organization and maintainability. It separates the different types of message structs (request, reply, event, and error) into their own dedicated files, each with a corresponding test file. The request parsing functions have also been moved intorequest_messages.goto live alongside the request structs they create. Finally, all structs within the new files have been sorted by their associated opcode as requested.PR created automatically by Jules for task 12024349921956840092