JSONPath

RFC-9535 compliant JSONPath query evaluator for Elixir, with 100% passing rate for the JSONPath Compliance Test Suite

Installation

Add json_path to your list of dependencies in mix.exs:

def deps do
  [
    {:json_path, "~> 0.2"}
  ]
end

Usage

JSONPath supports string keys only.

You can pass the JSONPath query expression as a string

iex(1)> root = [%{"a" => %{"b" => "c"}}, %{"b" => %{"a" => 1}}]
iex(2)> query = "$..a"
iex(3)> JSONPath.evaluate(root, query)
{:ok, [%{"b" => "c"}, 1]}

Or if you plan use the same query multiple times, you can build the expression once for better performance

iex(1)> {:ok, query} = JSONPath.build("$[1]")
iex(2)> JSONPath.evaluate([], query)
{:ok, []}

iex(3)> JSONPath.evaluate(["a", "b", "c"], query)
{:ok, ["b"]}

Attempting to build invalid JSONPath expressions returns helpful error messages

iex(1)> JSONPath.build("$[?length(@.elems)]")
{:error,
 %JSONPath.Error{
   type: :invalid_expression,
   expression: "length(@['elems'])",
   message: "comparison operator expected"
 }}

iex(2)> JSONPath.evaluate([%{"name" => "Alice"}], "$[?match(@.name)]")
{:error,
 %JSONPath.Error{
   type: :invalid_expression,
   expression: "match(@['name'])",
   message: "got 1 argument but 'match' expects 2 arguments"
 }}

Notes and considerations

• JSONPath always returns a list of nodes, as specified by RFC-9535, even for expressions that could return at most one element such as $.x.
• Atom keys are not supported.
• JSON Path expects I-RegExp style regular expressions, which are a limited version of regular expressions made to be compatible and easy to implement in most languages. This library instead allows for any Elixir-valid regular expression.