+hjHdZddlmZddlmZGddejZdS)a tl;dr: See FutureModelForm's docstring. Many apps provide new related managers to extend your django models with. For example, django-tagulous provides a TagField which abstracts an M2M relation with the Tag model, django-gm2m provides a GM2MField which abstracts an relation, django-taggit provides a TaggableManager which abstracts a relation too, django-generic-m2m provides RelatedObjectsDescriptor which abstracts a relation again. While that works pretty well, it gets a bit complicated when it comes to encapsulating the business logic for saving such data in a form object. This is three-part problem: - getting initial data, - saving instance attributes, - saving relations like reverse relations or many to many. Django's ModelForm calls the model field's ``value_from_object()`` method to get the initial data. ``FutureModelForm`` tries the ``value_from_object()`` method from the form field instead, if defined. Unlike the model field, the form field doesn't know its name, so ``FutureModelForm`` passes it when calling the form field's ``value_from_object()`` method. Django's ModelForm calls the form field's ``save_form_data()`` in two occasions: - in ``_post_clean()`` for model fields in ``Meta.fields``, - in ``_save_m2m()`` for model fields in ``Meta.virtual_fields`` and ``Meta.many_to_many``, which then operate on an instance which as a PK. If we just added ``save_form_data()`` to form fields like for ``value_from_object()`` then it would be called twice, once in ``_post_clean()`` and once in ``_save_m2m()``. Instead, ``FutureModelForm`` would call the following methods from the form field, if defined: - ``save_object_data()`` in ``_post_clean()``, to set object attributes for a given value, - ``save_relation_data()`` in ``_save_m2m()``, to save relations for a given value. For example: - a generic foreign key only sets instance attributes, its form field would do that in ``save_object_data()``, - a tag field saves relations, its form field would do that in ``save_relation_data()``. )chain)formscPeZdZdZfdZfdZdZddZedZ xZ S) FutureModelForma/ ModelForm which adds extra API to form fields. Form fields may define new methods for FutureModelForm: - ``FormField.value_from_object(instance, name)`` should return the initial value to use in the form, overrides ``ModelField.value_from_object()`` which is what ModelForm uses by default, - ``FormField.save_object_data(instance, name, value)`` should set instance attributes. Called by ``save()`` **before** writing the database, when ``instance.pk`` may not be set, it overrides ``ModelField.save_form_data()`` which is normally used in this occasion for non-m2m and non-virtual model fields. - ``FormField.save_relation_data(instance, name, value)`` should save relations required for value on the instance. Called by ``save()`` **after** writing the database, when ``instance.pk`` is necessarily set, it overrides ``ModelField.save_form_data()`` which is normally used in this occasion for m2m and virtual model fields. For complete rationale, see this module's docstring. ctt|j|i||jD]9\}}t |ds||j||j|<:dS)z:Override that uses a form field's ``value_from_object()``.value_from_objectN) superr__init__fieldsitemshasattrrinstanceinitial)selfargskwargsnamefield __class__s M/var/www/html/e360mart/e360mart_env/lib/python3.11/site-packages/dal/forms.pyr zFutureModelForm.__init__Ns-ot$$-t>v>>>;,,.. N NKD%5"566 !&!8!8!M!MDL    N Nc  tt||jD]K\}}t |ds||j||j |dLdS);Override that uses the form field's ``save_object_data()``.save_object_dataN) r r _post_cleanr r r rr cleaned_dataget)rrrrs rrzFutureModelForm._post_cleanXs ot$$00222;,,..  KD%5"455   " " !%%dD11       rcj|j}|jj}|jj}|jj}g}|jD]M\}}t |ds||j|||||Nt|dg}|st|dg}t|j |D]d} | j |vr t | ds|r | j |vr)|r | j |vr5| j |vr&| |j|| j edS)rsave_relation_datavirtual_fieldsprivate_fieldssave_form_dataN)r_metaexcluder rr r rappendgetattrr many_to_manyrr") rrr$r optshandledrrr fs r _save_m2mzFutureModelForm._save_m2mfs( *$"}";,,.. ! !KD%5"677   $ $ T"    NN4 !'7<< A$T+;R@@Nt(.99 F FAv  1.//  !&.. 16W,,v%%   QV0DEEE F FrTc|jr8td|jjjd|jjjrdndd|r.|j|n |j|_ |jS)z"Backport from Django 1.9+ for 1.8.zThe z could not be createdchangedz" because the data didn't validate.) errors ValueErrorrr# object_name_stateaddingsaver+save_m2m)rcommits rr4zFutureModelForm.saves ; *M'333!%!5!<KII)KK   + M   NN    !NDM}rcZfdjdDS)z Create a list of url patterns, to be called in url.py. Example:: urlpattern.append(*ModelForm.as_url()) Iterate over the fields to call the as_url() method from the GenericForeignKeyField cjg|]/\}}t|jd|0S)as_url)r rr9).0keyvalueclss r z+FutureModelForm.as_urls..sK   Uu11 LL     rdeclared_fields)__dict__r )r=s`ras_urlszFutureModelForm.as_urlssB    !l+<=CCEE    r)T) __name__ __module__ __qualname____doc__r rr+r4 classmethodrA __classcell__)rs@rrr7s,NNNNN     'F'F'FR&  [     rrN)rE itertoolsrdjangor ModelFormrrrrLsv//b{ { { { { eo{ { { { { r