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
Copy file name to clipboardExpand all lines: CHANGELOG.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,11 @@
1
1
# Python JSONPath Change Log
2
2
3
+
## Version 0.4.0
4
+
5
+
**IETF JSONPath Draft compliance**
6
+
7
+
-**Behavioral change.** When applied to a JSON object, filters now have an implicit preceding wildcard selector. This is now consistent with applying filters to arrays and adheres to the IETF JSONPath Internet Draft.
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -290,7 +290,7 @@ And this is a list of areas where we deviate from the [IETF JSONPath draft](http
290
290
- The root token (default `$`) is optional.
291
291
- Paths starting with a dot (`.`) are OK. `.thing` is the same as `$.thing`, as is `thing`, `$[thing]` and `$["thing"]`.
292
292
- Nested filters are not supported.
293
-
- We don't treat filter expressions without a comparison as existence test, but an "is truthy" test. See the "Existence of non-singular queries" example in the IETF JSONPath draft.
293
+
- We don't treat filter expressions without a comparison as existence test, but an "is truthy" test.
294
294
295
295
And this is a list of features that are uncommon or unique to Python JSONPath.
0 commit comments