jsocol / jsocol/django-adminplus
Django 1.8.7 register decorator didn't work
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 602
- Forks
- 76
- PR merge metrics
- No merged PRs in 30d
Description
We had one model that was using the decorator rather than the explicit call and after adding adminplus that model disappeared from our admin screens.
Changing it over to the other call worked although I thought I read that it should have worked so not sure I think there must be a bug there.. Happy to investigate further if someone can point me in the right direction.
Contributor guide
No contributing guide indexed for this repository
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
Reproduce the issue with Django 1.8.7 and django-adminplus using the decorator-based registration, then compare it with the explicit registration call that works. Trace the admin registration path to determine why the decorated model disappears from the admin screens. Done means decorator registration behaves like the explicit call, with a regression test covering both forms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100