Hi Claude,
Thanks for your feedback, it's a great idea to make modelform a callable
registry instance or something.
In some project we're going to try to acheive this kind of coupling and
work with Python components instead of templates for example:
status = CharField(components=dict(form=MyStat
Le vendredi 24 août 2018 11:35:43 UTC+2, Jamesie Pic a écrit :
>
> Thank for your feedback.
>
> It's the eternal misunderstanding of django's pattern, confusion between
> table, and model, model is de factores what couples table and form, I've
> posted articles about it already. I call this the e
Thank for your feedback.
It's the eternal misunderstanding of django's pattern, confusion between
table, and model, model is de factores what couples table and form, I've
posted articles about it already. I call this the elephant in the room but
if I'm the only one to see it it means it's my mista
Not sure that's what's being suggested here James?
But I'm -1 on this because it's adding more coupling between models and
forms.
Also Jamesie, can't you just subclass in your ModelAdmin to
replace get_form / View classes to replace get_form_class and achieve the
same thing? As far as I understan
I'd be -1 on anything that encourages people to use ModelForm with all
fields included by default; that's asking for mass-assignment security
holes.
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubs
Hi all,
Currently when you want a model to be edited from a custom modelform, you
need to make use of that new modelform manually in your create/update views
and admin.
Would it be possible to add a new overridable method in the model to
generate a default modelform ?
Then, default create/update
