#25227: Add utility method `get_updated_model()` to `ModelForm`
-------------------------------------+-------------------------------------
Reporter: candeira | Owner: candeira
Type: | Status: assigned
Cleanup/optimization |
Component: Forms | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by akaariai):
These methods seem like a good addition. The save(do_not_save=True) API
isn't the best one in Django...
However we do need dedicated tests for the new methods as they are part of
public API. Also, we need dedicated documentation for the new methods.
I don't see what side effects save(commit=False) has when compared to
get_updated_model[s]()?
--
Ticket URL: <https://code.djangoproject.com/ticket/25227#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.9302641a8fe482a09b630513b3d9950f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
