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
It seems there's a naming convention there: despite the config names being case-insensitive, they don't usually have dashes in them. Git went so far as to deprecate some dash spellings (kebab case) in favor or dash-less. And they're usually documented in lowerCamelCase (a.k.a. dromedary case).
I was looking at my git config and realized delta configuration requires the dashes. Can we make them optional so delta.lineNumbers work just as well as delta.line-numbers?
The text was updated successfully, but these errors were encountered:
It seems there's a naming convention there: despite the config names being case-insensitive, they don't usually have dashes in them. Git went so far as to deprecate some dash spellings (kebab case) in favor or dash-less. And they're usually documented in lowerCamelCase (a.k.a. dromedary case).
I was looking at my git config and realized delta configuration requires the dashes. Can we make them optional so
delta.lineNumbers
work just as well asdelta.line-numbers
?The text was updated successfully, but these errors were encountered: