* Breaking change: For unwrapped results, return undefined instead of false upon failure to find path (to allow distinguishing of undefined--a non-allowed JSON value--from the valid JSON, null or false) and return the exact value upon falsy single results (in order to allow return of null)
* Continue work on new class-based API and object-based arguments (with option to run new queries via evaluate() method without resupplying config)
* Allow new preventEval=true option
* Allow new callback option to allow a callback function to execute as each final result node is obtained
* Support "parent" and "parentProperty" for resultType along with "all" (which also includes "path" and "value" together)
* Support "." within properties
* Support custom @parent, @parentProperty, @property (in addition to custom property @path) inside evaluations
* Support a custom operator ("~") to allow grabbing of property names
* Fix for @path in index/property evaluations
* Expose cache on JSONPath.cache for those who wish to preserve and reuse it
* Expose class methods `toPathString` 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)
* Allow ^ as property name
* Update README with more examples, APIs, and better code comments; update tests
* Add tests for callback, custom properties, "all" return type, properties, return (path) type, toPath
* Obscure JSON.stringify fix
* Add self to contributor list
Fix MD
Forgot to utilize temp vars
Add number to JSON types list in README
Allow type operators: JavaScript types (@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).
Change to simpler heading style; add Todos section
Add a type test to the README (and move its actaul test to the examples test file)
Fix MD
Fix toPathString() for typed operator
Merge branch 'typed-values' into todos
Merge branch 'todos' into type-test-to-readme