add v + doc dsc

Author: besok

CHANGELOG.md

@@ -51,4 +51,8 @@
     - Performance improvements
     - Change the contract for the struct of errors
 - **`0.7.0`**
-    - Bug fixes and api changes
+    - Bug fixes and api changes
+- **`0.7.1`**
+    - add Display to JsonPath
+- **`0.7.2`**
+    - add JsonLike trait

Cargo.toml

@@ -1,7 +1,7 @@
 [package]
 name = "jsonpath-rust"
 description = "The library provides the basic functionality to find the set of the data according to the filtering query."
-version = "0.7.0"
+version = "0.7.2"
 authors = ["BorisZhguchev <[email protected]>"]
 edition = "2021"
 license = "MIT"

README.md

@@ -244,22 +244,26 @@ This is enum type which represents:
 
 - `Slice` - a point to the passed original json
 - `NewValue` - a new json data that has been generated during the path( for instance length operator)
-- `NoValue` - indicates there is no match between given json and jsonpath in the most cases due to absent fields or inconsistent data.
+- `NoValue` - indicates there is no match between given json and jsonpath in the most cases due to absent fields or
+  inconsistent data.
 
 To extract data there are two methods, provided on the `value`:
 
 ```rust
 let v:JsonPathValue<Value> =...
 v.to_data();
-v.slice_or(&some_dafault_value)
+v.slice_or( & some_dafault_value)
 ```
 
 ### Find
 
 there are 4 different functions to find data inside a `value`.
-All take references, to increase reusability. Especially json parsing and jsonpath parsing can take significant time, compared to a simple find.
+All take references, to increase reusability. Especially json parsing and jsonpath parsing can take significant time,
+compared to a simple find.
 
-The methods `find`, `find_as_path`, `find_slice` and `find_slice_ptr` take the same inputs, but handle them differently depending on your usecase. They are further described in the [docs](https://docs.rs/jsonpath-rust/latest/jsonpath_rust/enum.JsonPath.html#implementations).
+The methods `find`, `find_as_path`, `find_slice` and `find_slice_ptr` take the same inputs, but handle them differently
+depending on your usecase. They are further described in
+the [docs](https://docs.rs/jsonpath-rust/latest/jsonpath_rust/enum.JsonPath.html#implementations).
 
 ```rust
 use jsonpath_rust::{JsonPath, JsonPathValue};
@@ -289,12 +293,18 @@ https://docs.rs/jsonpath-rust/latest/jsonpath_rust/parser/model/enum.JsonPath.ht
 The internal structure of the `JsonPathIndex` can be found here:
 https://docs.rs/jsonpath-rust/latest/jsonpath_rust/parser/model/enum.JsonPathIndex.html
 
+### JsonLike
+
+The library provides a trait `JsonLike` that can be implemented for any type.
+This allows you to use the `JsonPath` methods on your own types.
+
 ## How to contribute
 
 TBD
 
 ## How to update version
- - update files
- - commit them
- - add tag `git tag -a v<Version> -m "message"`
- - git push origin <tag_name>
+
+- update files
+- commit them
+- add tag `git tag -a v<Version> -m "message"`
+- git push origin <tag_name>

benches/regex.rs

@@ -1,6 +1,6 @@
 use criterion::{criterion_group, criterion_main, Criterion};
 use jsonpath_rust::{JsonPath, JsonPathQuery};
-use serde_json::json;
+use serde_json::{json, Value};
 use std::str::FromStr;
 
 struct SearchData {
@@ -23,7 +23,7 @@ fn regex_perf_test_without_reuse() {
 }
 
 fn json_path_compiling() {
-    let _v = JsonPath::from_str(PATH).unwrap();
+    let _v = JsonPath::<Value>::from_str(PATH).unwrap();
 }
 
 pub fn criterion_benchmark(c: &mut Criterion) {