Skip to content

Conversation

@gabe565
Copy link
Contributor

@gabe565 gabe565 commented Oct 11, 2024

This is one of my two solutions to fix #40.

Add a -casesensitive flag, which disables all generation of lower-cased values.

  • This required more code changes up front, and users have to know to add the -casesensitive flag, but the resulting functionality completely eliminates the possibility of choosing the incorrect value.
  • This method also has the benefit of not changing existing code after users update enumer. Code would only change after adding -casesensitive.
  • Unfortunately, users may not realize there is a -casesensitive flag and could introduce bugs in their code in the future.

Fixes #40

@gabe565 gabe565 force-pushed the add-casesensitive-flag branch from 1e2c502 to 5ff271c Compare October 11, 2024 06:57
@gabe565 gabe565 force-pushed the add-casesensitive-flag branch from ec013e8 to b152fa0 Compare October 11, 2024 07:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Flag for case sensitive in <Type>String(s string)

1 participant