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
supports referencing envs in hotkeys #2420
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.
@wjiec Very cool! Thank you for this update Jayson!!
Not sure if I have a better attr name for you.
Let me know if any of the alternates makes better sense??
internal/config/hotkey.go
Outdated
@@ -19,6 +19,7 @@ type HotKey struct { | |||
ShortCut string `yaml:"shortCut"` | |||
Description string `yaml:"description"` | |||
Command string `yaml:"command"` | |||
Navigable bool `yaml:"navigable"` |
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.
Navigable feels a bit odd. Not sure if I have a better term tho?
Was thinking asBreadCrumb
, 'asTab' or asChild
or keepHistory
??
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.
I think keepHistory
is better :)
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.
@wjiec Sold! Thank you for the updates Jayson.
Cool! |
* supports referencing envs in hotkeys * add testcase for hotkeys * rename attr name to keepHistory
* supports referencing envs in hotkeys * add testcase for hotkeys * rename attr name to keepHistory
related issues: #2334.
This PR introduces a new setting to the hotkeys, allowing one to choose if the current view should be kept. for example: