Simplify MultipleContentTypeField boilerplate #98
Labels
good first issue
Great issues for newcomers!
type: housekeeping
Changes to the application which do not directly impact the end user
Projects
Milestone
Proposed Changes
Followup to #92 - Provide a custom
__init__
method for the MultipleContentTypeField class, so that we can more simply instantiate it, along the lines of:Possibly something similar should also be implemented for
CSVMultipleContentTypeField
?Justification
Currently there's a lot of boilerplate in instantiating a MultipleContentTypeField, particularly in constructing and ordering the queryset correctly.
It would be nice if we could instantiate it with a simple
feature="relationships"
and have the appropriate queryset get automatically constructed and ordered. It also probably makes sense for this field to default to using aStaticSelect2Multiple
widget instead of requiring that to be manually specified each time.The text was updated successfully, but these errors were encountered: