-
Notifications
You must be signed in to change notification settings - Fork 0
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
style: add category property to commands #55
base: main
Are you sure you want to change the base?
style: add category property to commands #55
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.
So you've added "category": "GitGuardian"
for all commands, but in your screenshot, where is the GitGuardian:
prefix coming from? Isn't going to be doubled? (or is it already coming from this PR?)
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.
Thank you ! 🙏
a81f467
to
5fe2255
Compare
It's coming from the I've added a commit to fix some case issues in the views names. |
Context
The display of the commands was not standardized: some commands were not prepended by GitGuardian, and the others were using gitguardian instead of GitGuardian.
What has been done
Update
package.json
to group GitGuardian commands into theGitGuardian
category.Validation
Open the command palette and verify that GitGuardian commands are prepended by GitGuardian: