-
Couldn't load subscription status.
- Fork 135
Fix: keyboard shortcut issues #146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello @chikoski, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
Summary of Changes
This pull request addresses keyboard shortcut issues in the application. It modifies the way keyboard events are handled, ensuring actions are triggered on key press rather than key release. Additionally, it enables users to send messages using the Enter key in the chat screen without requiring the Shift key.
Highlights
- Keyboard Event Handling: The pull request modifies the
isKeyPressedfunction to trigger actions onKeyDownevents instead ofKeyUpevents. - Send Message with Enter Key: The pull request enables sending messages in the chat screen by pressing the Enter key, removing the previous requirement of pressing Shift + Enter.
Changelog
- app/src/main/java/com/google/android/samples/socialite/MainActivity.kt
- Modified the keyboard shortcut for sending messages to not require the Shift key.
- app/src/main/java/com/google/android/samples/socialite/ui/chat/ChatScreen.kt
- Removed unused imports related to key event types.
- Modified the
scrollWithKeyboardsmodifier to handle scrolling events on key press instead of key release. - Modified the
InputBarcomposable to allow sending messages with just the Enter key.
- app/src/main/java/com/google/android/samples/socialite/ui/chat/component/KeyEvent.kt
- Modified the
isKeyPressedfunction to check forKeyEventType.KeyDownby default.
- Modified the
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| Feature | Command | Description |
|---|---|---|
| Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
| Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
| Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
| Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
A key is pressed,
The message swiftly takes flight,
Chat flows with ease.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
The pull request addresses keyboard shortcut issues, enhancing the user experience by handling shortcuts only when a key is pressed and enabling message sending with the Enter key on the chat screen. The changes look good overall, but there are a few points that could be improved.
Summary of Findings
- KeyEventType Removal: The removal of
KeyEventTypecheck might lead to unintended behavior ifKeyUpandKeyDownevents are not handled correctly. It's crucial to ensure that the logic still works as expected without explicitly checking the event type. - Redundant
shouldShiftBePressedParameter: InInputBar, theshouldShiftBePressedparameter was removed from theisKeyPressedfunction call. This might affect the expected behavior when using Shift + Enter. - Keyboard Shortcut for Sending Messages: The change in
MainActivity.ktremoves theMETA_SHIFT_ONmodifier for the send message shortcut. This means the user no longer needs to press Shift + Enter to send a message using the keyboard shortcut, which aligns with the pull request description.
Merge Readiness
The pull request addresses the keyboard shortcut issues as described. However, the removal of KeyEventType check and the change in shouldShiftBePressed parameter should be carefully reviewed to ensure no regressions are introduced. I am unable to directly approve the pull request, and other reviewers should review and approve this code before merging. I would recommend addressing the medium severity issue before merging.
This pull request fixes several issues on keyboard shortcuts. Specifically, it changes the behaviors as follows: