id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
27704	contrib.postgres.ArrayField with choices should use TypedMultipleChoiceField as its default form field class	Carl Meyer	Anvesh Mishra	"Currently the contrib.postgres ArrayField implements no special handling for choices, which makes it pretty useless with choices; you can specify your choices as a list of possible arrays for the ArrayField to contain. This is, I suppose, consistent in some technical sense, but rarely if ever useful in practice. It's very handy to use an ArrayField with choices to implement a multiple-choice field. We already have a `TypedMultipleChoiceField` form field in Django, so the implementation for this is just a trivial enhancement to the `ArrayField.formfield` method: if `self.choices` is set, use `TypedMultipleChoiceField` as the form class, with the `base_field` used to determine the expected type.

Any objections to this before I submit a PR for it?
"	New feature	assigned	contrib.postgres	dev	Normal				Accepted	1	0	0	1	0	0