You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you specify a widget option for AutoCompleteSelectMultipleField it is ignored and overwritten, but AutoCompleteSelectField will let you specify one (as long as it is the correct type). It looks like this might also be the case for AutoCompleteField.
Alternatively or additionally, AutoCompleteField seems to allow passing in widget attributes - making that work consistently for all the field classes would be useful and might remove the need for specifying the widget.
The text was updated successfully, but these errors were encountered:
There shouldn't really be a case where you specify a custom widget. This whole django-ajax-selects thing is basically just the widgets and processing what they return.
and claims to be for issue 9, but that is incorrect. It would be better to remove the option entirely and make the code look more consistent on each one.
@crucialfelix my use case was that I wanted to specify placeholder text for the input. There was a way to do it for the select field but not the multiple select field, and since I couldn't do it consistently I had to skip it for now.
I agree, it would probably be better to remove the widget option and make the field objects consistent for passing widget attributes in.
If you specify a widget option for AutoCompleteSelectMultipleField it is ignored and overwritten, but AutoCompleteSelectField will let you specify one (as long as it is the correct type). It looks like this might also be the case for AutoCompleteField.
This just needs to have the logic from AutoCompleteSelectField duplicated for the other init methods:
https://github.com/crucialfelix/django-ajax-selects/blob/develop/ajax_select/fields.py#L125-L134
Alternatively or additionally, AutoCompleteField seems to allow passing in widget attributes - making that work consistently for all the field classes would be useful and might remove the need for specifying the widget.
The text was updated successfully, but these errors were encountered: