ModelAdmin.formfield_overrides should look at field attributes

[Marek Stępniowski]

ModelAdmin.formfield_overrides should look at field attributes in addition to field class, when choosing which widget to use in template. The most important use case here is the choices attribute, as it's likely that user will want to render fields with choices differently (i.e. as select) than fields without choices (which can be a normal input).

After #19303 is merged, current mechanism will allow users to override widget choice for all fields with a certain class. It won't be possible to choose different widget for normal fields and fields with choices, short of overriding the ModelForm. That's not optimal.

[Simon Meers]

As stated the ​/ docs, formfield_overrides "provides a quick-and-dirty way to override some of the Field options for use in the admin". If you want to do something more complicated than a simple per-field-class override, you should look into overriding ModelAdmin.formfield_for_dbfield. Whilst not overly elegant, it will allow you to completely customise the form fields based on whatever properties you like without "overriding the ModelForm". You may also be interested in ​/ ModelAdmin.formfield_for_choice_field in this instance.

Feel free to propose details of a more elegant solution, though please bear in mind backwards-compatibility concerns. You may also find the details and outcome of #17924 relevant, involving a similar proposal for ModelForms in general.