Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Should support field ordering #3

Open
maroux opened this issue Jun 11, 2015 · 0 comments
Open

Should support field ordering #3

maroux opened this issue Jun 11, 2015 · 0 comments

Comments

@maroux
Copy link

maroux commented Jun 11, 2015

In some cases, it's desirable for the data to be ordered, in others, it's mandatory for the deserialization to respect order - example, deserializing Django objects with reverse fkey relations.
@maroux maroux mentioned this issue Jun 11, 2015
Open
maroux pushed a commit to maroux/serpy that referenced this issue Jun 11, 2015
Allow provision for ordering fields when setting them.
1f6d4e3 
When deserializing Django objects, reverse relations need to be deserialized after primary key field

Fixes clarkduvall#3
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@maroux