Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle enums that are not all-caps better #31

Open
yifanmai opened this issue Aug 10, 2016 · 1 comment
Open

Handle enums that are not all-caps better #31

yifanmai opened this issue Aug 10, 2016 · 1 comment

Comments

@yifanmai
Copy link

We have a number of persisted models with enum types in which the string representations of the enums are camel-cased. Courier only supports all-caps enums, so these enums cannot be migrated to Courier.

Possible solutions:

  • Allow enum symbols to be camel-cased, rather than enforcing all enums to be all-caps.
  • Allow alias values for enum symbols i.e. allow the string representation of the enum symbols to be specified.
@kchen-coursera
Copy link

Actually, courier seems to handle non all-caps enums just fine in my experience. It's just a matter of inconsistency with our naming convention

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

No branches or pull requests

2 participants