#35330: The update of related objects fails in the admin when the related model
is
camel case.
-------------------------------+--------------------------------------
Reporter: devin13cox | Owner: devin13cox
Type: Bug | Status: assigned
Component: contrib.admin | Version: 5.0
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 1
-------------------------------+--------------------------------------
Comment (by Natalia Bidart):
Replying to [comment:3 devin13cox]:
> Replying to [comment:2 devin13cox]:
> > If I want to use the test models from the PR listed in the ticket,
should I just wait until that PR gets eventually merged in? Or is it
preferred to make any changes here independent of another ticket (and
subsequently make alterations to admin to work for this ticket)?
>
> Or if there is another preferred way to approach this given the close
relationship between this ticket, the one mentioned in the description,
and #35331, I am open to suggestions!
Hi! My suggestion would be to progress with this ticket independently of
the other tickets. Have you checked if any of the existing models would
help building your testcase?
--
Ticket URL: <https://code.djangoproject.com/ticket/35330#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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018e809959c1-e3e0ae6d-9b87-496d-9a4e-d5a88beae9c1-000000%40eu-central-1.amazonses.com.