#33714 closed New feature (duplicate)
Better admin support for ArrayFields where the base_field has choices
Reported by: | Jaap Roes | Owned by: | nobody |
---|---|---|---|
Component: | contrib.admin | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Currently the admin doesn't really work well when registering a model that has a ArrayField of which the base_field has choices e.g.:
class Post(model.Model): category = ArrayField( models.CharField(choices=[ ('FASHION', 'Fashion'), ('STYLE', 'Style'), ('SPORTS', 'Sports'), ('FUN', 'Fun'), ], max_length=8), size=2, blank=True, default=list )
For example, the edit form uses a simple text input to edit the choices instead of a MultipleChoiceField
. Adding the field to list_display
will show the raw values, not the display names. Adding the field to list_filter
will only show filter options of combinations used in the database (stringified arrays).
Change History (4)
comment:1 by , 2 years ago
comment:2 by , 2 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
I think we can treat this as a duplicate of #32328.
follow-up: 4 comment:3 by , 2 years ago
I don't agree that this is a duplicate. This is about a much narrower case where an ArrayField is used to wrap another field with choices. Basically using the ArrayField as a M2M where the "other" side is a fixed set of options, instead of a database table. The most similar ticket I can find is #24858, which has been resolved but for a much more esoteric case (imho) where the ArrayField itself has choices.
comment:4 by , 2 years ago
Replying to Jaap Roes:
I don't agree that this is a duplicate. This is about a much narrower case where an ArrayField is used to wrap another field with choices. Basically using the ArrayField as a M2M where the "other" side is a fixed set of options, instead of a database table. The most similar ticket I can find is #24858, which has been resolved but for a much more esoteric case (imho) where the ArrayField itself has choices.
My understanding is that we could have a better widget. I don't think it's worth improving only this rather niche case.
We have some workarounds in place to make it work in our projects.
Instead of
ArrayField
we use:For list filters we use:
and for list display purposes we define methods on the admin class that call this little helper function:
It would be nice if we can get rid of these workarounds and have this working in Django Admin without any extra code.