fix: unresponsive selections in custom command menu #1416
Merged
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.
RE: https://sourcegraph.slack.com/archives/C05AGQYD528/p1697105184992049
This PR fixes the issuses reported by Philipp where `` does not work in Custom Commands Menu. This issue was caused by the previous update when
description
has become a required field.description
fieldlast five used custom commands
not showing up in the same menuThis fixes an issue where commands with null descriptions would not be run when selected.
Test plan
Custom Commands
Configure Custom Commands...
andNew Custom Command...
These options should now work when building from this branch.
Other commands should still work as expected.