-
Notifications
You must be signed in to change notification settings - Fork 301
Order #1094
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.
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
Order #1094
Conversation
probably not a feasible idea yet, or some minor adjustment would fix the failed tests |
Thanks for the hinter. this is something to consider but I will need to do more research what the drawbacks could be of this change. however your PR does not change it properly as the ordered dict constructur expected a list of tuples. a dict uses the key:value syntax. So you would need to change that as well. |
thanks, I also need some more research / study here. |
I had a look into this a bit more and found this article which summarizes the difference between Py 3.7+ dict and The main points to use
In the JSON:API spec there does not seem to be any specific ordering. So if an API returns attributes as first key and then relationships or the other way around, the two resources are still considered the same. Comparing two objects where the order of the keys are different should actually still be equal, which is not the case when using In that case, it could even be considered a bug that we use I try to clean up your PR here, so the tests are green. If you get to it first, feel free to update it yourself. |
Seems that you do not have given the permission that I can update this PR. Anyway, it will be good to have another set of eyes look over it. Therefore, I have started continuing this PR in #1132 There are more occurrences of |
Fixes #
Try python dict instead of OrderedDict
Checklist
CHANGELOG.md
updated (only for user relevant changes)AUTHORS