#36801: `construct_change_message`call `form.changed_data` after check if is add
-------------------------------------+-------------------------------------
Reporter: Rodolfo Becerra | Owner: Rodolfo
Type: | Becerra
Cleanup/optimization | Status: new
Component: contrib.admin | Version:
Severity: Normal | Resolution:
Keywords: | Triage Stage:
construct_change_message | Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Adam Johnson):
* has_patch: 0 => 1
* resolution: needsinfo =>
* status: closed => new
Comment:
Rodolfo created this ticket at my encouragement, after he showed me a diff
of the change he meant. I think the description didn't quite do it
justice, so I've created a PR to show what he meant. I think it's a pretty
clear optimization.
--
Ticket URL: <https://code.djangoproject.com/ticket/36801#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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019ba9a96a1f-69da47e1-bd1c-4387-a07c-31175a77a242-000000%40eu-central-1.amazonses.com.
