Doesn't matter that much what your style is, as long as it is applied automatically and the linter doesn't just harass the programmer.
I find your last remark curious, as I sometimes feel like having the "wrong" capitalization for the language is the "right" thing to do when using external sources.
For example, when writing against this Zigbee spec, in JS/TS I feel like having a named parameter args.AckedTransitions may be superior to renaming it to args.ackedTransitions.
Am I redacted? Should I commit toaster bath?
Thanks for the response. Regarding your capitalization, if that works for you and your team, then I don't have a problem. For me personally, I find it visually jarring when something differs epecially when there are multiple capitalization methods in a single class. In the C# world, I think mixed capitalization is not very common. As well as Visual Studio 2017 with .editorconfig can define capitalization conventions and flag violations with a warning. Which I've done so these would have shown as warnings for D if he were using VS 2017.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Doesn't matter that much what your style is, as long as it is applied automatically and the linter doesn't just harass the programmer.
I find your last remark curious, as I sometimes feel like having the "wrong" capitalization for the language is the "right" thing to do when using external sources.
For example, when writing against this Zigbee spec, in JS/TS I feel like having a named parameter
args.AckedTransitionsmay be superior to renaming it toargs.ackedTransitions.Am I redacted? Should I commit toaster bath?
Thanks for the response. Regarding your capitalization, if that works for you and your team, then I don't have a problem. For me personally, I find it visually jarring when something differs epecially when there are multiple capitalization methods in a single class. In the C# world, I think mixed capitalization is not very common. As well as Visual Studio 2017 with .editorconfig can define capitalization conventions and flag violations with a warning. Which I've done so these would have shown as warnings for D if he were using VS 2017.