-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Fix the title and text of the Discard Changes prompt #2706
Changes from all commits
51a5580
ee03a0b
2f6b7b9
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -32,7 +32,7 @@ type GuiConfig struct { | |
ScrollHeight int `yaml:"scrollHeight"` | ||
ScrollPastBottom bool `yaml:"scrollPastBottom"` | ||
MouseEvents bool `yaml:"mouseEvents"` | ||
SkipUnstageLineWarning bool `yaml:"skipUnstageLineWarning"` | ||
SkipDiscardChangeWarning bool `yaml:"skipDiscardChangeWarning"` | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is a breaking change, but I didn't bother doing something about it. Since the warning prompt mentions the config, it's easy enough to fix it manually. We could however consider rewriting the config file with the renamed property, now that that's possible. Worth it? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think it's worth rewriting the config. Note that the existing code in |
||
SkipStashWarning bool `yaml:"skipStashWarning"` | ||
SidePanelWidth float64 `yaml:"sidePanelWidth"` | ||
ExpandFocusedSidePanel bool `yaml:"expandFocusedSidePanel"` | ||
|
@@ -397,17 +397,17 @@ type CustomCommandMenuOption struct { | |
func GetDefaultConfig() *UserConfig { | ||
return &UserConfig{ | ||
Gui: GuiConfig{ | ||
ScrollHeight: 2, | ||
ScrollPastBottom: true, | ||
MouseEvents: true, | ||
SkipUnstageLineWarning: false, | ||
SkipStashWarning: false, | ||
SidePanelWidth: 0.3333, | ||
ExpandFocusedSidePanel: false, | ||
MainPanelSplitMode: "flexible", | ||
Language: "auto", | ||
TimeFormat: "02 Jan 06", | ||
ShortTimeFormat: time.Kitchen, | ||
ScrollHeight: 2, | ||
ScrollPastBottom: true, | ||
MouseEvents: true, | ||
SkipDiscardChangeWarning: false, | ||
SkipStashWarning: false, | ||
SidePanelWidth: 0.3333, | ||
ExpandFocusedSidePanel: false, | ||
MainPanelSplitMode: "flexible", | ||
Language: "auto", | ||
TimeFormat: "02 Jan 06", | ||
ShortTimeFormat: time.Kitchen, | ||
Theme: ThemeConfig{ | ||
ActiveBorderColor: []string{"green", "bold"}, | ||
InactiveBorderColor: []string{"default"}, | ||
|
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 would like a way to track which 'version' of the config we're on so that we only need to run migrations if we are behind. This has a few benefits:
We could store this version on the config itself. What do you think?
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 don't think this would work. If we read a config file that doesn't have a version, there's no way to tell whether this is a new user who just created a new config file for the latest version, or if it's an old config file from before we started to put a version in the file. Unless we require the user to manually add the correct version when they initially create a config file, which I don't think we should.
I also disagree with some of the alleged downsides:
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.
Good points. Let's go with your approach then :)