Changelog
0.11.2 (Dec 12, 2015 10:36pm)
Changelog
0.11.1 (Dec 12, 2015 10:11pm)
Changelog
0.11.0 (Dec 12, 2015)
undefined
instead
of false
upon failure to find path (to allow distinguishing of
undefined
--a non-allowed JSON value--from the valid JSON values,
null
or false
) and return the exact value upon falsy single
results (in order to allow return of null
)jsonPath.eval()
; use new class-based API insteadself
instead of window
export, allow JSONPath
to be trivially imported into web workers, without breaking
compatibility in normal scenarios. See MDN on selfevaluate()
method without resupplying config)preventEval=true
and autostart=false
option@boolean()
, @number()
,
@string()
), other fundamental JavaScript types (@null()
, @object()
,
@array()
), the JSONSchema-added type, @integer()
, and the following
non-JSON types that can nevertheless be used with JSONPath when querying
non-JSON JavaScript objects (@undefined()
, @function()
, @nonFinite()
).
Finally, @other()
is made available in conjunction with a new callback
option, otherTypeCallback
, can be used to allow user-defined type
detection (at least until JSON Schema awareness may be provided).@parent
, @parentProperty
, @property
(in
addition to custom property @path
) inside evaluations~
) to allow grabbing of property names$
for retrieval of root, and document this as well as
$..
behaviorJSONPath.cache
for those who wish to preserve and
reuse ittoPathString
for converting a path as array
into a (normalized) path as string and toPathArray
for the reverse (though
accepting unnormalized strings as well as normalized)^
as property name.
within properties@path
in index/property evaluationsChangelog
0.10.0 (Oct 23, 2013)
^
@path
in test statementsChangelog
0.9.0 (Mar 28, 2012)
vm.runInNewContext
in place of eval