Replies: 2 comments 1 reply
-
|
I've recently discovered that VSCode highlights Makes one of the bigger reasons why I'd prefer enum properties cased like such. I, however, haven't yet found any other syntax highlighter that does this, e.g. GitHub's markdown: // Syntax highlight test
const enumTest = Enum.SOME_VALUE;
const miscTest = Enum.SomeValue; |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Seems like the convention we are using is TypeScript's1, and by extension, C#'s2 (language documentation wise, at least) Footnotes |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I've been adopting Discord.js's way of naming enum values—
PascalCasefor both the enum object and its value names—but I've made the discovery recently that the convention, according to a Stack Overflow answer with a few notable sources, isPascalCasefor the enum andSCREAMING_SNAKE_CASEfor the value names. I quite favor this convention and have been adopting that instead, as it differentiates values from the rest of the notation.I'd hate for this to be taken as a request to rename all enum values with this kind of casing—I know how destructive that would be—but I'd like to bring this up as a pedant about conventions.
Beta Was this translation helpful? Give feedback.
All reactions