Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
define a required field with no default
See original GitHub issueThe code automatically sets the first choice as the default value: https://github.com/5monkeys/django-enumfield/blob/master/django_enumfield/db/fields.py#L16-L17
I think this behavior is misleading because if someone defines a field with no default, he expects the field to have no default assigned so that an error is raised if the field is also required.
Right now, it’s impossible to have a required field (null=False) with no default that would work as expected in the admin.
enum.EnumField(STATUSES, blank=True, null=False)
Setting default=None obviously doesn’t work as the whole code assumes there is a value.
Issue Analytics
- State:
- Created 8 years ago
- Comments:9 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
wow this is very misleading and README should clarify.
@clovis1122 I’m not sure I follow. What is the issue you want to solve exactly? An example of a model would help me understand.