Enforce enum names (enhancement) #2835
Comments
Closed
paul-dingemans
added a commit
that referenced
this issue
Oct 19, 2024
This property allows enum entry names to be restricted to: * `upper_cases`: an enum entry may only contain uppercases, and underscores, and digits, and dicritics on letters and strokes * `camel_cases`: an enum entry may only contain CamelCase values, including digits, and dicritics on letters and strokes) * `upper_or_camel_case`: allows both the `upper_cases` and `camel_cases` styles as defined in the Kotlin Coding Conventions Closes #2835
8 tasks
paul-dingemans
added a commit
that referenced
this issue
Oct 20, 2024
…#2839) This property allows enum entry names to be restricted to: * `upper_cases`: an enum entry may only contain uppercases, and underscores, and digits, and dicritics on letters and strokes * `camel_cases`: an enum entry may only contain CamelCase values, including digits, and dicritics on letters and strokes) * `upper_or_camel_case`: allows both the `upper_cases` and `camel_cases` styles as defined in the Kotlin Coding Conventions Closes #2835
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Rule behavior
#635 enforces naming within enums as per Kotlin Coding Conventions. The style guide is liberal here, allowing 2 options.
This is great, but we'd like an enhancement to the existing rule so we can configure which of the two options are our project convention, so we can stay consistent across our codebase.
The text was updated successfully, but these errors were encountered: