#29894: Read-only fields in ModelAdmin should not be placed at the end
-------------------------------+--------------------------------------
Reporter: Jannik Schürg | Owner: nobody
Type: New feature | Status: closed
Component: contrib.admin | Version: master
Severity: Normal | Resolution: wontfix
Keywords: readonly | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by Carlton Gibson):
* status: new => closed
* resolution: => wontfix
Comment:
Hi Jannik,
Thanks for the input and the discussion on the PR.
I'm going to say no to this one as-is.
This would affect almost all users of the admin, changing a long-standing
behaviour. That doesn't seem justified given that `fields` and `fieldsets`
are already available. (Use those if you want to control ordering.)
I'm happy if you want to ask for further opinions on the
DevelopersMailingList. (Personally, I quite like the existing behaviour
and am used to it, so I'd be -1 on making the change there.)
--
Ticket URL: <https://code.djangoproject.com/ticket/29894#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.4c4c3027609bc57bb341411fc84bd535%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
