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
Use choice keys, not descriptions, for enums #19
Comments
morgante
changed the title
Use choice keys, not descriptions for enums
Use choice keys, not descriptions, for enums
Oct 12, 2016
morgante
added a commit
to morgante/graphene-django
that referenced
this issue
Oct 14, 2016
morgante
added a commit
to morgante/graphene-django
that referenced
this issue
Oct 14, 2016
syrusakbary
added a commit
that referenced
this issue
Oct 15, 2016
Fix #19 by using choice keys as enum keys, not choice descriptions
Hispar
added a commit
to Hispar/graphene-django
that referenced
this issue
May 24, 2019
…actor Restore pytest and improve coverage
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, the automatically generated choices for Django fields correspond to the text labels passed in not the keys.
This is problematic because changing labels in the future would lead to all your enum values being updated. It's also contrary to what I would expect as a user.
The text was updated successfully, but these errors were encountered: