Changes between Initial Version and Version 1 of Ticket #33321, comment 2


Ignore:
Timestamp:
Dec 2, 2021, 12:56:50 AM (3 years ago)
Author:
James Pic

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #33321, comment 2

    initial v1  
    77It's fine for me though, in our apps we don't advertise to declare formfields anymore, but rather to [https://yourlabs.io/oss/djhacker monkey patch Django formfield()] method which actually lets Django think it's generating the foreign key fields and the decorated it with RelatedFieldWidgetWrapper, which has also [https://github.com/jonashaag/django-addanother been copy/pasted into an external app] so it could be reusable outside the admin, by me.
    88
    9 The most proper solution IMHO is to extract RelatedFieldWidgetWrapper outside from django.contrib.admin and put in in django.forms but that's not going to happen neither.
     9The most proper solution IMHO is to extract RelatedFieldWidgetWrapper outside from django.contrib.admin and put in in django.forms but that's not going to happen neither. We'd have to at least begin integrating ESM, and change jQuery for custom HTMLElements to deal with element lifecycle, if we want to be able provide native fields with solid JS integration.
Back to Top