-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Code Quality: Use action description when selecting via arrow keys #17227
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.
Pull Request Overview
This PR improves the user experience when selecting suggestions via arrow keys by ensuring the displayed text comes from command descriptions rather than their codes. Key changes include updating the text display in the omnibar suggestion items and refining the command palette mode logic in the navigation toolbar.
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
File | Description |
---|---|
src/Files.App/ViewModels/UserControls/NavigationToolbarViewModel.cs | Replaced command.Code with command.Description for the text properties and related comparisons in suggestion items. |
src/Files.App/UserControls/NavigationToolbar.xaml.cs | Updated the command palette mode handling by extracting the current mode into a local variable and iterating over commands based on their description. |
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 wise LGTM
Resolved / Related Issues
To prevent extra work, all changes to the Files codebase must link to an approved issue marked as
Ready to build
. Please insert the issue number following the hashtag with the issue number that this Pull Request resolves.Steps used to test these changes
Stability is a top priority for Files and all changes are required to go through testing before being merged into the repo. Please include a list of steps that you used to test this PR.