-
Notifications
You must be signed in to change notification settings - Fork 18
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
Hashmap key order shouldn't matter #47
Comments
Comparing different versions, it looks like it was introduced in 2.9.202. My first guess is that this was caused by #45. @latacora-paul, do you have time to look into this? |
RutledgePaulV
added a commit
to RutledgePaulV/deep-diff2
that referenced
this issue
Jun 19, 2023
Sure, here's a PR that stops using the sequential del+ins that is causing the issue for maps and adds a test for this scenario: |
RutledgePaulV
added a commit
to RutledgePaulV/deep-diff2
that referenced
this issue
Jun 19, 2023
alysbrooks
added a commit
that referenced
this issue
Jul 24, 2023
## Added ## Fixed Varying key order in maps should produce a consistent diff (#47) ## Changed
plexus
added a commit
that referenced
this issue
Feb 17, 2024
## Added - Diff / preserve metadata on collections ## Fixed Varying key order in maps should produce a consistent diff (#47) ## Changed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It shouldn't matter in which order I add keys to a hashmap:
Expected
Actual
The
:age
key is removed and re-added:The text was updated successfully, but these errors were encountered: