#23780: Easy to use natural keys from a tuple on meta
-------------------------------------+-------------------------------------
Reporter: scrummyin | Owner: nobody
Type: New feature | Status: new
Component: Core | Version: master
(Serialization) | Resolution:
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by scrummyin):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
Sorry, I just realized I broke some other tests. After I broke them and
took another look at them, I think I didn't break them, but there were
already messed up. I have adjusted those tests for what I think is the
proper use case. I believe in their original form the serializer output
the models in the wrong order. I reorder the data in the test and got it
to work. When I looked at the new order I realized that the new order
reflected the decencies correctly. A membership had fk's to person and
group and it should have come after those two objects. This is correctly
reflected in the revised tests. With this git commit
https://github.com/scrummyin/django/commit/ce6d437c72de478c681a934509a186cb242f84f7.
--
Ticket URL: <https://code.djangoproject.com/ticket/23780#comment:1>
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.1e56f5820279a55d5f8dc87b049e2cf3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
