Add is-subset and is-subset-ci operator modes for list comparison#150
Merged
jeffkala merged 2 commits intonetworktocode:developfrom Mar 11, 2026
Merged
Conversation
pszulczewski
approved these changes
Mar 10, 2026
jeffkala
approved these changes
Mar 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue #149
This PR introduces two new operator modes to jdiff:
These operators allow validation of list-valued fields by checking whether the extracted list is a subset of a reference list. jdiff currently supports scalar comparisons but does not provide a built-in mechanism to validate that an extracted list is contained within an allowed set. This PR adds subset comparison operators to address that use case.
is-subset: Validates that the extracted list is a subset of the reference listis-subset-ci: Same as is-subset but case-insensitiveExample:
Enhancement to
associate_key_of_my_value()A small improvement was required to support extraction paths where a single selected field contains a list value
[*].[$id$,include_trusted_domains]. Previously, such cases raisedValueError("Key's value len != from value len")because the function interpreted list elements as separate field values. This required a small enhancement inassociate_key_of_my_value()to correctly interpret cases where a single extracted field contains a list value instead of treating the list elements as separate field values.Example JSON:
[ { "id": "DOMAIN1.COMPANY.COM", "include_trusted_domains": [ "COMPANY.COM", "domain1.company.com", "domain2.company.COM", "domain3.company.com", "test.com" ] } ]