You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The comparator must be extended to accept different validation options. The first option to be implemented is the ability to ignore different JSON fields based on specific JSONPaths. (more details about JSONPath here with the newest revision here; the second one is crazy long, they are here just for reference).
The JSONPaths that we will be supporting first will cover these cases:
$.store.book[0].title - target a specific field.
$..author | $.store..price - target a field with the specified name, wherever it is under a specific parent.
$.store.* - target all fields under a specific parent. $..* falls into this category, but I am curious of what use-cases this could cover.
The Builder already has a method to configure this (it's commented out).
The text was updated successfully, but these errors were encountered:
codemental
changed the title
JsonPath ignore
Add JsonPath ignore feature to Comparator
Jan 19, 2024
codemental
changed the title
Add JsonPath ignore feature to Comparator
Add JSONPath ignore feature to Comparator
Jan 19, 2024
The comparator must be extended to accept different validation options. The first option to be implemented is the ability to ignore different JSON fields based on specific JSONPaths. (more details about JSONPath here with the newest revision here; the second one is crazy long, they are here just for reference).
The JSONPaths that we will be supporting first will cover these cases:
$.store.book[0].title
- target a specific field.$..author
|$.store..price
- target a field with the specified name, wherever it is under a specific parent.$.store.*
- target all fields under a specific parent.$..*
falls into this category, but I am curious of what use-cases this could cover.The
Builder
already has a method to configure this (it's commented out).The text was updated successfully, but these errors were encountered: