#27273: Make usage of construct_change_message easier outside of admin
-------------------------------------+-------------------------------------
Reporter: Alexey Rogachev | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: contrib.admin | Version: master
Severity: Normal | Resolution:
Keywords: admin, form | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* type: Uncategorized => Cleanup/optimization
Comment:
I guess making it a static method could be fine (except that it's
backwards-incompatible for `ModelAdmin` subclasses), but I'm not sure if
reorganizing the code and making it a function (at the expense of
readability) is worthwhile. Also, that would remove the ability for
subclasses to customize the method (absent the introduction of another
helper function).
--
Ticket URL: <https://code.djangoproject.com/ticket/27273#comment:3>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.547d367fd401d6b23cf506bfce6c81f6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
