django-commons / django-commons/django-enum
translated properties can't be symmetric
Open
Nobody has claimed this yet.
question
- Dominant language
- Python
- Stars
- 110
- Forks
- 6
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 4
Description
Document this/determine any workaround or what least bad behavior should be.
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
No files, tests, or entry points are named in the issue. Start by reproducing the asymmetric behavior of translated properties in the Django enum field, then determine whether a workaround or a documented least-bad behavior is possible. Done means documenting the observed limitation and agreed workaround or expected behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100