-
Notifications
You must be signed in to change notification settings - Fork 6
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
Add a nested object case with non-determinism #68
Conversation
The non-determinism comes from the descendant traversal ordering rules as well as from the unordered nature of objects.
@gregsdennis Please could you take a look. I want to make sure we are all on the same page with these tests. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me. Passes for me, and the permutations look right.
@jg-rp can you run your thing to verify the permutations, please?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works for my implementation.
Have done. Looks good to me. |
@glyn not sure why this can't merge. Can you investigate, please? |
Will do. AFK ATM.
…On Thu, 21 Mar 2024, 07:09 Greg Dennis, ***@***.***> wrote:
@glyn <https://github.com/glyn> not sure why this can't merge. Can you
investigate, please?
—
Reply to this email directly, view it on GitHub
<#68 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAXF2MATDVQ7EMTMQV5CD3YZKBRZAVCNFSM6AAAAABE6VXC7OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJRGM2TAMJVGY>
.
You are receiving this because you were mentioned.Message ID:
<jsonpath-standard/jsonpath-compliance-test-suite/pull/68/c2011350156@
github.com>
|
@gregsdennis The branch protection rule I added was over-zealous and was locking |
The non-determinism comes from the descendant traversal ordering rules as well as from the unordered nature of objects.
(Please note that this was accidentally pushed to main earlier and then reverted. A branch protection rule is now in place!)