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
Is there a way to set the search field on a model when using the GenericForeignKeyModelField, similar to how you can with the Select2GenericForeignKeyModelField by passing a tuples to model_choices?
In a GenericForeignKeyModelField that second part of the tuple (the search field) gets ignored and still looks for a "name" field regardless.
Thanks!
The text was updated successfully, but these errors were encountered:
I see copy and pasted code, but I don't use that at this time... meanwhile reviews are open for refactoring pull requests.
I'm trying to refactor this from the ground up by generalizing the as_url() system, but I'm experimenting combining that with djhacker.formfield at the same time while we're at it so the whole chain is automated at once, in the spirit of DAL v2, but without the un-maintainable code I did naively at that time 10 years ago.
Pushed to as_url branch but I'm not done there...
Is there a way to set the search field on a model when using the
GenericForeignKeyModelField
, similar to how you can with theSelect2GenericForeignKeyModelField
by passing a tuples tomodel_choices
?In a
GenericForeignKeyModelField
that second part of the tuple (the search field) gets ignored and still looks for a "name" field regardless.Thanks!
The text was updated successfully, but these errors were encountered: