django-commons / django-commons/django-enum
Expose internal enum field types?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 110
- Forks
- 6
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 4
Description
EnumField will automatically trigger migrations when the underlying enum changes in such a way that the database needs alterations (mostly column size overflows).
Some users may want to more explicitly specify the enum type - say use EnumPositiveSmallIntegerField directly instead of relying on EnumField to resolve it.
EnumPositiveSmallIntegerField should still update check constraints automatically when necessary.
This may just involve adding these types to __all__ and documenting this usage...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating EnumField and the EnumPositiveSmallIntegerField type, then inspect how these fields are exported and documented. Verify how explicit enum field types handle migrations and check-constraint updates, and add coverage showing the documented usage works as intended.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- database
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100