You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the issue tracker for open issues that relate to the same feature, before opening a new one.
This issue only relates to a single feature. I will open new issues for any other features.
Is your feature request related to a problem?
According to Go's wiki:
Error strings should not be capitalized (unless beginning with proper nouns or acronyms) or end with punctuation, since they are usually printed following other context.
However, our context (error dialogs) are usually showed to the end/final user, and I believe texts in error dialogs should start capitalized, and end with a period.
Is it possible to construct a solution with the existing API?
Yes
Describe the solution you'd like to see.
By default, every error dialog should start capitalized and end with a period. I believe most languages follows this "convention" (?).
To disable, maybe you could use a function like:
a:=dialog.NewError(fmt.Errorf("something went very wrong in our side, error code: %v", errInt))
a.DisableAutoCaps()
a.Show()
The text was updated successfully, but these errors were encountered:
I am a bit torn on this one (not saying no it; just not sure). If you need to show something more readable, would it not be better to use the information dialog? You cloud attach some extra information and be more helpful for the user.
Given that this is just a helper for what may be unexpected errors it seems like something reasonable to add, given that Go insists we have no capital letters at the beginning of the text.
Checklist
Is your feature request related to a problem?
According to Go's wiki:
However, our context (error dialogs) are usually showed to the end/final user, and I believe texts in error dialogs should start capitalized, and end with a period.
See discussion on Discord.
Is it possible to construct a solution with the existing API?
Yes
Describe the solution you'd like to see.
By default, every error dialog should start capitalized and end with a period. I believe most languages follows this "convention" (?).
To disable, maybe you could use a function like:
The text was updated successfully, but these errors were encountered: