jsonpath-rw 1.1

JSONPath Syntax

The JSONPath syntax supported by this library includes some additional features and omits some problematic features (those that make it unportable). In particular, some new operators such as | and where are available, and parentheses are used for grouping not for callbacks into Python, since with these changes the language is not trivially associative. Also, fields may be quoted whether or not they are contained in brackets.

Atomic expressions:

Jsonpath operators:

Also jsonpath1 | jsonpath2 for union (but I have not convinced Github-Flavored Markdown to allow me to put that in a table)

Field specifiers ( field ):

Array specifiers ( idx ):

Programmatic JSONPath

If you are programming in Python and would like a more robust way to create JSONPath expressions that does not depend on a parser, it is very easy to do so directly, and here are some examples:

• Root()

• Slice(start=0, end=None, step=None)

• Fields('foo', 'bar')

• Index(42)

• Child(Fields('foo'), Index(42))

• Where(Slice(), Fields('subfield'))

• Descendants(jsonpath, jsonpath)

Extensions

• Path data: The result of JsonPath.find provide detailed context and path data so it is easy to traverse to parent objects, print full paths to pieces of data, and generate automatic ids.

• Automatic Ids: If you set jsonpath_rw.auto_id_field to a value other than None, then for any piece of data missing that field, it will be replaced by the JSONPath to it, giving automatic unique ids to any piece of data. These ids will take into account any ids already present as well.

• Named operators: Instead of using @ to reference the currently object, this library uses `this`. In general, any string contained in backquotes can be made to be a new operator, currently by extending the library.

More to explore

There are way too many jsonpath implementations out there to discuss. Some are robust, some are toy projects that still work fine, some are exercises. There will undoubtedly be many more. This one is made for use in released, maintained code, and in particular for programmatic access to the abstract syntax and extension. But JSONPath at its simplest just isn’t that complicated, so you can probably use any of them successfully. Why not this one?

The original proposal, as far as I know:

• JSONPath - XPath for JSON by Stefan Goessner.

Contributors

• Kenn Knowles (@kennknowles)

Copyright and License

Copyright 2013- Kenneth Knowles

Licensed under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.