csonpath 0.17.0__tar.gz → 0.19.0__tar.gz

{csonpath-0.17.0 → csonpath-0.19.0}/Makefile

@@ -5,7 +5,7 @@ YYJSON_LDFLAGS=$(shell pkg-config --libs yyjson)
 
 include config.mk
 
-all: test-json-c-get-a test-json-update test-json-filter test-json-subpath test-json-c-array-root test-json-filter-and-missing-key test-json-get-array-big-index test-json-union test-json-audit-bugs test-json-crash-vectors test-json-my-fuzz
+all: test-json-c-get-a test-json-update test-json-filter test-json-subpath test-json-c-array-root test-json-filter-and-missing-key test-json-get-array-big-index test-json-union test-json-audit-bugs test-json-crash-vectors test-json-my-fuzz test-json-regex-overflow
 
 YYJSON_TESTS=test-yyjson
 
@@ -15,7 +15,7 @@ bench:
 bench-clean:
 	make -C bench clean
 
-.PHONY: all clean tests pip-dev pip-dev bench bench-clean tests-cli
+.PHONY: all clean tests pip-dev pip-dev bench bench-clean tests-cli tests-rust cov
 
 CFLAGS+= -Wall -Wextra -Wno-unused-function -Wno-unused-parameter -O0 -g
 
@@ -52,10 +52,19 @@ test-json-crash-vectors: tests/json-c/crash-vectors.c csonpath_json-c.h csonpath
 test-json-my-fuzz: tests/json-c/my_fuzz.c csonpath_json-c.h csonpath_my_fuzzing.h csonpath.h csonpath_do.h
 	$(CC) tests/json-c/my_fuzz.c $(EXTRA_FILES) $(JSON_C_CFLAGS) $(CFLAGS) -Wno-format -I./ -o test-json-my-fuzz $(JSON_C_LDFLAGS) $(LDFLAGS)
 
-test-yyjson: tests/yyjson/test-yyjson.c csonpath_yyjson.h csonpath.h csonpath_do.h
+test-json-regex-overflow: tests/json-c/regex-overflow.c csonpath_json-c.h csonpath.h csonpath_do.h
+	$(CC) tests/json-c/regex-overflow.c $(EXTRA_FILES) $(JSON_C_CFLAGS) $(CFLAGS) -Wno-format -I./ -o test-json-regex-overflow $(JSON_C_LDFLAGS) $(LDFLAGS)
+
+test-yyjson: tests/yyjson/test-yyjson.c csonpath_yyjson_const.h csonpath.h csonpath_do.h
 	$(CC) tests/yyjson/test-yyjson.c $(EXTRA_FILES) $(YYJSON_CFLAGS) $(CFLAGS) -Wno-format -I./ -o test-yyjson $(YYJSON_LDFLAGS) $(LDFLAGS)
 
-tests-c: test-json-c-get-a test-json-update test-json-filter test-json-subpath test-json-c-array-root test-json-filter-and-missing-key test-json-get-array-big-index test-json-union test-json-audit-bugs test-json-crash-vectors test-yyjson test-json-my-fuzz
+test-yyjson-mixed: tests/yyjson/test-yyjson-mixed.c csonpath_yyjson.h csonpath_yyjson_const.h csonpath_yyjson_mut.h csonpath.h csonpath_do.h
+	$(CC) tests/yyjson/test-yyjson-mixed.c $(EXTRA_FILES) $(YYJSON_CFLAGS) $(CFLAGS) -Wno-format -I./ -o test-yyjson-mixed $(YYJSON_LDFLAGS) $(LDFLAGS)
+
+test-multi-backend-prefix: tests/multi-backend-prefix.c csonpath_json-c.h csonpath_yyjson.h csonpath_yyjson_const.h csonpath_yyjson_mut.h csonpath.h csonpath_do.h
+	$(CC) tests/multi-backend-prefix.c $(EXTRA_FILES) $(JSON_C_CFLAGS) $(YYJSON_CFLAGS) $(CFLAGS) -Wno-format -I./ -o test-multi-backend-prefix $(JSON_C_LDFLAGS) $(YYJSON_LDFLAGS) $(LDFLAGS)
+
+tests-c: test-json-c-get-a test-json-update test-json-filter test-json-subpath test-json-c-array-root test-json-filter-and-missing-key test-json-get-array-big-index test-json-union test-json-audit-bugs test-json-crash-vectors test-yyjson test-yyjson-mixed test-json-my-fuzz test-multi-backend-prefix test-json-regex-overflow
 	./test-json-c-get-a
 	./test-json-update
 	./test-json-filter
@@ -67,7 +76,10 @@ tests-c: test-json-c-get-a test-json-update test-json-filter test-json-subpath t
 	./test-json-audit-bugs
 	./test-json-crash-vectors
 	./test-yyjson
+	./test-yyjson-mixed
 	./test-json-my-fuzz
+	./test-multi-backend-prefix
+	./test-json-regex-overflow
 
 csonpath: cli/csonpath_cli.c csonpath_json-c.h csonpath.h csonpath_do.h
 	$(CC) cli/csonpath_cli.c $(EXTRA_FILES) $(JSON_C_CFLAGS) $(CFLAGS) -I./ -o csonpath $(JSON_C_LDFLAGS) $(LDFLAGS)
@@ -81,8 +93,36 @@ pip-dev:
 tests-py: pip-dev
 	python -m pytest
 
-tests: tests-py tests-c
+tests-rust:
+	cargo test --manifest-path rust/Cargo.toml
+
+cov:
+	$(MAKE) clean
+	rm -rf coverage-c coverage-c.html coverage-py coverage-rust build
+	find . -name '*.gcov' -delete
+	$(MAKE) CFLAGS='--coverage -O0 -g' LDFLAGS='--coverage' tests-c
+	$(MAKE) CFLAGS='--coverage -O0 -g' LDFLAGS='--coverage' csonpath
+	bash tests/cli/run.sh ./csonpath
+	CFLAGS='--coverage -O0' LDFLAGS='--coverage' python setup.py build_ext --inplace --force
+	python -m coverage run -m pytest
+	python -m coverage html -d coverage-py
+	python -m gcovr -r . \
+		--gcov-object-directory "$$(ls -d build/temp.* 2>/dev/null | head -1)" \
+		--filter 'csonpath\.h' --filter 'csonpath_do\.h' --filter 'csonpath_python\.c' \
+		--html-details coverage-c.html
+	PATH="$$HOME/.cargo/bin:$$PATH" \
+		LLVM_COV="$$(find $$HOME/.rustup/toolchains -name llvm-cov -print -quit)" \
+		LLVM_PROFDATA="$$(find $$HOME/.rustup/toolchains -name llvm-profdata -print -quit)" \
+		cargo llvm-cov --manifest-path rust/Cargo.toml --html --output-dir coverage-rust
+	@echo "Coverage reports:"
+	@echo "  coverage-c.html"
+	@echo "  coverage-py/index.html"
+	@echo "  coverage-rust/html/index.html"
+
+tests: tests-py tests-c tests-cli tests-rust
 
 clean:
-	rm -rvf test-json-c-get-a test-json-update test-json-filter test-json-subpath test-json-c-array-root test-json-filter-and-missing-key test-json-get-array-big-index test-json-union test-json-audit-bugs test-json-crash-vectors test-yyjson test-json-my-fuzz csonpath
+	rm -rvf test-json-c-get-a test-json-update test-json-filter test-json-subpath test-json-c-array-root test-json-filter-and-missing-key test-json-get-array-big-index test-json-union test-json-audit-bugs test-json-crash-vectors test-yyjson test-yyjson-mixed test-json-my-fuzz test-multi-backend-prefix test-json-regex-overflow csonpath
+	find . -name '*.gcda' -delete
+	find . -name '*.gcno' -delete
 

{csonpath-0.17.0/csonpath.egg-info → csonpath-0.19.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: csonpath
-Version: 0.17.0
+Version: 0.19.0
 Description-Content-Type: text/markdown
 License-File: LICENSE
 Provides-Extra: dev
@@ -13,9 +13,9 @@ Dynamic: license-file
 
 [![Project Sandbox](https://docs.outscale.com/fr/userguide/_images/Project-Sandbox-yellow.svg)](https://docs.outscale.com/en/userguide/Open-Source-Projects.html)
 
-**csonpath** is a partial [JSONPath](https://goessner.net/articles/JsonPath/) implementation in C, with Python bindings. It allows you to query, update, and remove data from JSON objects using path expressions.
+**csonpath** is a partial [JSONPath](https://goessner.net/articles/JsonPath/) implementation in C. It is **backend-agnostic**: the same core engine can query, update, and remove data from any value representation that supports array, object, and scalar semantics—not just JSON.
 
-Unlike many JSONPath libraries, csonpath is **backend-agnostic**: it can work with any C library or environment that manipulates array, object, and scalar types—not just JSON. Out of the box, backends for [json-c](https://github.com/json-c/json-c), [yyjson](https://github.com/ibireme/yyjson), Python and Rust (via `serde_json`) are provided.
+Out of the box it ships with C backends for [json-c](https://github.com/json-c/json-c) and [yyjson](https://github.com/ibireme/yyjson), plus language bindings for **Python** and **Rust**.
 
 ---
 
@@ -30,6 +30,7 @@ Unlike many JSONPath libraries, csonpath is **backend-agnostic**: it can work wi
 | Array index | `$.array[0]` | Access by zero-based index |
 | Wildcard `[*]` | `$.array[*].field` | Iterate all array elements |
 | Recursive descent `..` | `$..name` | Search recursively for a key |
+| Recursive descent wildcard `..*` | `$..*` | Return all descendants |
 | Union `,` (inside brackets) | `$['a','b']`, `$.array[0,1]`, `$.items[?n==1, ?n==2]` | Match all listed selectors at once |
 | OR fallback `\|` | `$.a \| $.b` | Try the left path first; fall back to the right one if it does not match. Only the first successful path is used. |
 | Filters | `$.items[?price > 10]` | Filter array elements |
@@ -37,6 +38,7 @@ Unlike many JSONPath libraries, csonpath is **backend-agnostic**: it can work wi
 | Multiple filters (`&`) | `$.items[?a=1 & b=2]` | Combine conditions |
 | Subpath expressions | `$.obj[$.key]` | Use JSON values as dynamic path keys |
 | `@` current object | `$.items[?@.price > 10]` | Reference the current element in filters |
+| Type selectors | `$..["@odata.id"]@string()`, `$.*@integer()` | Filter matches by JSON type (`string`, `integer`, `null`) |
 
 ### Operations
 - **Find First** — retrieve the first match.
@@ -63,6 +65,7 @@ Unlike many JSONPath libraries, csonpath is **backend-agnostic**: it can work wi
 - [C API Reference](#-c-api-reference)
 - [Python API Reference](#-python-api-reference)
 - [CLI](#%EF%B8%8F-cli)
+- [Using Multiple Backends](#-using-multiple-backends)
 - [Custom Backends](#-custom-backends)
 - [Running Tests](#-running-tests)
 - [Directory Structure](#-directory-structure)
@@ -73,12 +76,12 @@ Unlike many JSONPath libraries, csonpath is **backend-agnostic**: it can work wi
 
 ## 📦 Installation
 
-### Prerequisites
-- C compiler (`gcc` or `clang`)
-- [json-c](https://github.com/json-c/json-c) library (for C usage)
-- Python 3.x (for Python bindings)
+csonpath is a C library at its core. Pick the instructions for the language you want to use it from.
 
 ### C (json-c)
+
+**Prerequisites:** C compiler (`gcc`, `clang`, or `tcc`), [json-c](https://github.com/json-c/json-c).
+
 Just include the header in your project. There is no separate install step required:
 ```c
 #include "csonpath_json-c.h"
@@ -88,21 +91,23 @@ Make sure to link against `json-c` when compiling:
 gcc myapp.c -o myapp $(pkg-config --cflags --libs json-c)
 ```
 
-### C (Rust backend)
-The Rust backend is located in `rust/`. It builds both a safe Rust API and the C glue required by the csonpath core.
+### C (yyjson)
 
-```sh
-cd rust
-cargo build
-cargo test
-```
+**Prerequisites:** C compiler (`gcc`, `clang`, or `tcc`), [yyjson](https://github.com/ibireme/yyjson).
 
-To use it from C, include the backend header and link against the produced static library:
 ```c
-#include "rust/csonpath_rust_backend.h"
+#include "csonpath_yyjson.h"
+```
+
+Link against `yyjson` when compiling:
+```sh
+gcc myapp.c -o myapp $(pkg-config --cflags --libs yyjson)
 ```
 
 ### Python
+
+**Prerequisites:** Python 3.x.
+
 Install from PyPI:
 ```sh
 pip install csonpath
@@ -115,6 +120,23 @@ pip install .
 make pip-dev
 ```
 
+### Rust
+
+**Prerequisites:** Rust toolchain.
+
+The Rust crate is located in `rust/`. Build and test it with:
+```sh
+cd rust
+cargo build
+cargo test
+```
+
+To depend on it from another Rust project:
+```toml
+[dependencies]
+csonpath = { path = "rust" }
+```
+
 ---
 
 ## 🛠️ Usage
@@ -195,6 +217,8 @@ p.update_or_create_callback(dst, my_sync_fn, userdata)
 
 ## 📘 C API Reference
 
+The reference below uses the **json-c** backend as an example (`struct json_object *`). All backends expose the same functions with their own value type.
+
 ```c
 struct csonpath *csonpath_new(const char *path);
 ```
@@ -337,17 +361,47 @@ echo '{"a": 1, "b": 2}' | ./csonpath -d '$.b'
 
 ---
 
+## 🧩 Using Multiple Backends
+
+You can include more than one csonpath backend in the same translation unit, provided you prefix all but one of them to avoid symbol collisions. Define `CSONPATH_USE_PREFIX` before a backend header to prefix its API with the backend name.
+
+For example, to use both json-c and the immutable yyjson backend in the same file:
+
+```c
+#define CSONPATH_USE_PREFIX
+#include "csonpath_json-c.h"
+
+#undef CSONPATH_USE_PREFIX
+#include "csonpath_yyjson_const.h"
+```
+
+To use both yyjson backends (immutable and mutable) together, include the aggregator header:
+
+```c
+#include "csonpath_yyjson.h"
+```
+
+When using the mutable yyjson backend, assign the document pointer to `backend_ctx` before mutable operations:
+
+```c
+struct csonpath *mp = yyjson_mut_csonpath_new("$.a");
+mp->backend_ctx = mdoc;
+yyjson_mut_csonpath_update_or_create(mp, mroot, new_val);
+```
+
+---
+
 ## 🔌 Custom Backends
 
-csonpath is designed to be backend-agnostic. It can work with any data structure that supports array, object, and scalar semantics.
+csonpath is designed to be backend-agnostic. The C core manipulates opaque value pointers through a small set of macros, so it can work with any data structure that supports array, object, and scalar semantics.
 
-To create a custom backend, define the required macros and types in a header file (similar to `csonpath_json-c.h` or `csonpath_python.c`), then include your backend header before `csonpath.h`. This allows you to adapt csonpath for manipulating data in any format that supports array/object semantics, giving you full flexibility beyond just JSON.
+A backend is an adapter that implements those macros for a concrete value representation. To create a custom backend, define the required macros and types in a header file (similar to `csonpath_json-c.h` or `csonpath_yyjson.h`), then include your backend header before `csonpath.h`.
 
-For more details, see the existing backend implementations:
-- `csonpath_json-c.h` — json-c backend
-- `csonpath_yyjson.h` — yyjson backend
-- `csonpath_python.c` — Python backend
-- `rust/csonpath_rust_backend.h` — Rust / serde_json backend
+Existing backend adapters:
+- `csonpath_json-c.h` — json-c values
+- `csonpath_yyjson.h` — yyjson values
+- `csonpath_python.c` — Python C API values (used by the Python bindings)
+- `rust/csonpath_rust_backend.h` — Rust `serde_json::Value` (used by the Rust crate)
 
 ---
 
@@ -384,7 +438,7 @@ make tests
 | `csonpath_json-c.h` | json-c backend |
 | `csonpath_yyjson.h` | yyjson backend |
 | `csonpath_python.c` | Python C extension backend |
-| `rust/` | Rust backend (safe API, FFI, C glue) |
+| `rust/` | Rust crate and its C backend adapter |
 | `csonpath_my_fuzzing.h` | Fuzzer helpers (C) |
 | `tests/` | C and Python test suites |
 | `bench/` | Performance benchmarks |

{csonpath-0.17.0 → csonpath-0.19.0}/README.md

@@ -4,9 +4,9 @@
 
 [![Project Sandbox](https://docs.outscale.com/fr/userguide/_images/Project-Sandbox-yellow.svg)](https://docs.outscale.com/en/userguide/Open-Source-Projects.html)
 
-**csonpath** is a partial [JSONPath](https://goessner.net/articles/JsonPath/) implementation in C, with Python bindings. It allows you to query, update, and remove data from JSON objects using path expressions.
+**csonpath** is a partial [JSONPath](https://goessner.net/articles/JsonPath/) implementation in C. It is **backend-agnostic**: the same core engine can query, update, and remove data from any value representation that supports array, object, and scalar semantics—not just JSON.
 
-Unlike many JSONPath libraries, csonpath is **backend-agnostic**: it can work with any C library or environment that manipulates array, object, and scalar types—not just JSON. Out of the box, backends for [json-c](https://github.com/json-c/json-c), [yyjson](https://github.com/ibireme/yyjson), Python and Rust (via `serde_json`) are provided.
+Out of the box it ships with C backends for [json-c](https://github.com/json-c/json-c) and [yyjson](https://github.com/ibireme/yyjson), plus language bindings for **Python** and **Rust**.
 
 ---
 
@@ -21,6 +21,7 @@ Unlike many JSONPath libraries, csonpath is **backend-agnostic**: it can work wi
 | Array index | `$.array[0]` | Access by zero-based index |
 | Wildcard `[*]` | `$.array[*].field` | Iterate all array elements |
 | Recursive descent `..` | `$..name` | Search recursively for a key |
+| Recursive descent wildcard `..*` | `$..*` | Return all descendants |
 | Union `,` (inside brackets) | `$['a','b']`, `$.array[0,1]`, `$.items[?n==1, ?n==2]` | Match all listed selectors at once |
 | OR fallback `\|` | `$.a \| $.b` | Try the left path first; fall back to the right one if it does not match. Only the first successful path is used. |
 | Filters | `$.items[?price > 10]` | Filter array elements |
@@ -28,6 +29,7 @@ Unlike many JSONPath libraries, csonpath is **backend-agnostic**: it can work wi
 | Multiple filters (`&`) | `$.items[?a=1 & b=2]` | Combine conditions |
 | Subpath expressions | `$.obj[$.key]` | Use JSON values as dynamic path keys |
 | `@` current object | `$.items[?@.price > 10]` | Reference the current element in filters |
+| Type selectors | `$..["@odata.id"]@string()`, `$.*@integer()` | Filter matches by JSON type (`string`, `integer`, `null`) |
 
 ### Operations
 - **Find First** — retrieve the first match.
@@ -54,6 +56,7 @@ Unlike many JSONPath libraries, csonpath is **backend-agnostic**: it can work wi
 - [C API Reference](#-c-api-reference)
 - [Python API Reference](#-python-api-reference)
 - [CLI](#%EF%B8%8F-cli)
+- [Using Multiple Backends](#-using-multiple-backends)
 - [Custom Backends](#-custom-backends)
 - [Running Tests](#-running-tests)
 - [Directory Structure](#-directory-structure)
@@ -64,12 +67,12 @@ Unlike many JSONPath libraries, csonpath is **backend-agnostic**: it can work wi
 
 ## 📦 Installation
 
-### Prerequisites
-- C compiler (`gcc` or `clang`)
-- [json-c](https://github.com/json-c/json-c) library (for C usage)
-- Python 3.x (for Python bindings)
+csonpath is a C library at its core. Pick the instructions for the language you want to use it from.
 
 ### C (json-c)
+
+**Prerequisites:** C compiler (`gcc`, `clang`, or `tcc`), [json-c](https://github.com/json-c/json-c).
+
 Just include the header in your project. There is no separate install step required:
 ```c
 #include "csonpath_json-c.h"
@@ -79,21 +82,23 @@ Make sure to link against `json-c` when compiling:
 gcc myapp.c -o myapp $(pkg-config --cflags --libs json-c)
 ```
 
-### C (Rust backend)
-The Rust backend is located in `rust/`. It builds both a safe Rust API and the C glue required by the csonpath core.
+### C (yyjson)
 
-```sh
-cd rust
-cargo build
-cargo test
-```
+**Prerequisites:** C compiler (`gcc`, `clang`, or `tcc`), [yyjson](https://github.com/ibireme/yyjson).
 
-To use it from C, include the backend header and link against the produced static library:
 ```c
-#include "rust/csonpath_rust_backend.h"
+#include "csonpath_yyjson.h"
+```
+
+Link against `yyjson` when compiling:
+```sh
+gcc myapp.c -o myapp $(pkg-config --cflags --libs yyjson)
 ```
 
 ### Python
+
+**Prerequisites:** Python 3.x.
+
 Install from PyPI:
 ```sh
 pip install csonpath
@@ -106,6 +111,23 @@ pip install .
 make pip-dev
 ```
 
+### Rust
+
+**Prerequisites:** Rust toolchain.
+
+The Rust crate is located in `rust/`. Build and test it with:
+```sh
+cd rust
+cargo build
+cargo test
+```
+
+To depend on it from another Rust project:
+```toml
+[dependencies]
+csonpath = { path = "rust" }
+```
+
 ---
 
 ## 🛠️ Usage
@@ -186,6 +208,8 @@ p.update_or_create_callback(dst, my_sync_fn, userdata)
 
 ## 📘 C API Reference
 
+The reference below uses the **json-c** backend as an example (`struct json_object *`). All backends expose the same functions with their own value type.
+
 ```c
 struct csonpath *csonpath_new(const char *path);
 ```
@@ -328,17 +352,47 @@ echo '{"a": 1, "b": 2}' | ./csonpath -d '$.b'
 
 ---
 
+## 🧩 Using Multiple Backends
+
+You can include more than one csonpath backend in the same translation unit, provided you prefix all but one of them to avoid symbol collisions. Define `CSONPATH_USE_PREFIX` before a backend header to prefix its API with the backend name.
+
+For example, to use both json-c and the immutable yyjson backend in the same file:
+
+```c
+#define CSONPATH_USE_PREFIX
+#include "csonpath_json-c.h"
+
+#undef CSONPATH_USE_PREFIX
+#include "csonpath_yyjson_const.h"
+```
+
+To use both yyjson backends (immutable and mutable) together, include the aggregator header:
+
+```c
+#include "csonpath_yyjson.h"
+```
+
+When using the mutable yyjson backend, assign the document pointer to `backend_ctx` before mutable operations:
+
+```c
+struct csonpath *mp = yyjson_mut_csonpath_new("$.a");
+mp->backend_ctx = mdoc;
+yyjson_mut_csonpath_update_or_create(mp, mroot, new_val);
+```
+
+---
+
 ## 🔌 Custom Backends
 
-csonpath is designed to be backend-agnostic. It can work with any data structure that supports array, object, and scalar semantics.
+csonpath is designed to be backend-agnostic. The C core manipulates opaque value pointers through a small set of macros, so it can work with any data structure that supports array, object, and scalar semantics.
 
-To create a custom backend, define the required macros and types in a header file (similar to `csonpath_json-c.h` or `csonpath_python.c`), then include your backend header before `csonpath.h`. This allows you to adapt csonpath for manipulating data in any format that supports array/object semantics, giving you full flexibility beyond just JSON.
+A backend is an adapter that implements those macros for a concrete value representation. To create a custom backend, define the required macros and types in a header file (similar to `csonpath_json-c.h` or `csonpath_yyjson.h`), then include your backend header before `csonpath.h`.
 
-For more details, see the existing backend implementations:
-- `csonpath_json-c.h` — json-c backend
-- `csonpath_yyjson.h` — yyjson backend
-- `csonpath_python.c` — Python backend
-- `rust/csonpath_rust_backend.h` — Rust / serde_json backend
+Existing backend adapters:
+- `csonpath_json-c.h` — json-c values
+- `csonpath_yyjson.h` — yyjson values
+- `csonpath_python.c` — Python C API values (used by the Python bindings)
+- `rust/csonpath_rust_backend.h` — Rust `serde_json::Value` (used by the Rust crate)
 
 ---
 
@@ -375,7 +429,7 @@ make tests
 | `csonpath_json-c.h` | json-c backend |
 | `csonpath_yyjson.h` | yyjson backend |
 | `csonpath_python.c` | Python C extension backend |
-| `rust/` | Rust backend (safe API, FFI, C glue) |
+| `rust/` | Rust crate and its C backend adapter |
 | `csonpath_my_fuzzing.h` | Fuzzer helpers (C) |
 | `tests/` | C and Python test suites |
 | `bench/` | Performance benchmarks |

{csonpath-0.17.0 → csonpath-0.19.0/csonpath.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: csonpath
-Version: 0.17.0
+Version: 0.19.0
 Description-Content-Type: text/markdown
 License-File: LICENSE
 Provides-Extra: dev
@@ -13,9 +13,9 @@ Dynamic: license-file
 
 [![Project Sandbox](https://docs.outscale.com/fr/userguide/_images/Project-Sandbox-yellow.svg)](https://docs.outscale.com/en/userguide/Open-Source-Projects.html)
 
-**csonpath** is a partial [JSONPath](https://goessner.net/articles/JsonPath/) implementation in C, with Python bindings. It allows you to query, update, and remove data from JSON objects using path expressions.
+**csonpath** is a partial [JSONPath](https://goessner.net/articles/JsonPath/) implementation in C. It is **backend-agnostic**: the same core engine can query, update, and remove data from any value representation that supports array, object, and scalar semantics—not just JSON.
 
-Unlike many JSONPath libraries, csonpath is **backend-agnostic**: it can work with any C library or environment that manipulates array, object, and scalar types—not just JSON. Out of the box, backends for [json-c](https://github.com/json-c/json-c), [yyjson](https://github.com/ibireme/yyjson), Python and Rust (via `serde_json`) are provided.
+Out of the box it ships with C backends for [json-c](https://github.com/json-c/json-c) and [yyjson](https://github.com/ibireme/yyjson), plus language bindings for **Python** and **Rust**.
 
 ---
 
@@ -30,6 +30,7 @@ Unlike many JSONPath libraries, csonpath is **backend-agnostic**: it can work wi
 | Array index | `$.array[0]` | Access by zero-based index |
 | Wildcard `[*]` | `$.array[*].field` | Iterate all array elements |
 | Recursive descent `..` | `$..name` | Search recursively for a key |
+| Recursive descent wildcard `..*` | `$..*` | Return all descendants |
 | Union `,` (inside brackets) | `$['a','b']`, `$.array[0,1]`, `$.items[?n==1, ?n==2]` | Match all listed selectors at once |
 | OR fallback `\|` | `$.a \| $.b` | Try the left path first; fall back to the right one if it does not match. Only the first successful path is used. |
 | Filters | `$.items[?price > 10]` | Filter array elements |
@@ -37,6 +38,7 @@ Unlike many JSONPath libraries, csonpath is **backend-agnostic**: it can work wi
 | Multiple filters (`&`) | `$.items[?a=1 & b=2]` | Combine conditions |
 | Subpath expressions | `$.obj[$.key]` | Use JSON values as dynamic path keys |
 | `@` current object | `$.items[?@.price > 10]` | Reference the current element in filters |
+| Type selectors | `$..["@odata.id"]@string()`, `$.*@integer()` | Filter matches by JSON type (`string`, `integer`, `null`) |
 
 ### Operations
 - **Find First** — retrieve the first match.
@@ -63,6 +65,7 @@ Unlike many JSONPath libraries, csonpath is **backend-agnostic**: it can work wi
 - [C API Reference](#-c-api-reference)
 - [Python API Reference](#-python-api-reference)
 - [CLI](#%EF%B8%8F-cli)
+- [Using Multiple Backends](#-using-multiple-backends)
 - [Custom Backends](#-custom-backends)
 - [Running Tests](#-running-tests)
 - [Directory Structure](#-directory-structure)
@@ -73,12 +76,12 @@ Unlike many JSONPath libraries, csonpath is **backend-agnostic**: it can work wi
 
 ## 📦 Installation
 
-### Prerequisites
-- C compiler (`gcc` or `clang`)
-- [json-c](https://github.com/json-c/json-c) library (for C usage)
-- Python 3.x (for Python bindings)
+csonpath is a C library at its core. Pick the instructions for the language you want to use it from.
 
 ### C (json-c)
+
+**Prerequisites:** C compiler (`gcc`, `clang`, or `tcc`), [json-c](https://github.com/json-c/json-c).
+
 Just include the header in your project. There is no separate install step required:
 ```c
 #include "csonpath_json-c.h"
@@ -88,21 +91,23 @@ Make sure to link against `json-c` when compiling:
 gcc myapp.c -o myapp $(pkg-config --cflags --libs json-c)
 ```
 
-### C (Rust backend)
-The Rust backend is located in `rust/`. It builds both a safe Rust API and the C glue required by the csonpath core.
+### C (yyjson)
 
-```sh
-cd rust
-cargo build
-cargo test
-```
+**Prerequisites:** C compiler (`gcc`, `clang`, or `tcc`), [yyjson](https://github.com/ibireme/yyjson).
 
-To use it from C, include the backend header and link against the produced static library:
 ```c
-#include "rust/csonpath_rust_backend.h"
+#include "csonpath_yyjson.h"
+```
+
+Link against `yyjson` when compiling:
+```sh
+gcc myapp.c -o myapp $(pkg-config --cflags --libs yyjson)
 ```
 
 ### Python
+
+**Prerequisites:** Python 3.x.
+
 Install from PyPI:
 ```sh
 pip install csonpath
@@ -115,6 +120,23 @@ pip install .
 make pip-dev
 ```
 
+### Rust
+
+**Prerequisites:** Rust toolchain.
+
+The Rust crate is located in `rust/`. Build and test it with:
+```sh
+cd rust
+cargo build
+cargo test
+```
+
+To depend on it from another Rust project:
+```toml
+[dependencies]
+csonpath = { path = "rust" }
+```
+
 ---
 
 ## 🛠️ Usage
@@ -195,6 +217,8 @@ p.update_or_create_callback(dst, my_sync_fn, userdata)
 
 ## 📘 C API Reference
 
+The reference below uses the **json-c** backend as an example (`struct json_object *`). All backends expose the same functions with their own value type.
+
 ```c
 struct csonpath *csonpath_new(const char *path);
 ```
@@ -337,17 +361,47 @@ echo '{"a": 1, "b": 2}' | ./csonpath -d '$.b'
 
 ---
 
+## 🧩 Using Multiple Backends
+
+You can include more than one csonpath backend in the same translation unit, provided you prefix all but one of them to avoid symbol collisions. Define `CSONPATH_USE_PREFIX` before a backend header to prefix its API with the backend name.
+
+For example, to use both json-c and the immutable yyjson backend in the same file:
+
+```c
+#define CSONPATH_USE_PREFIX
+#include "csonpath_json-c.h"
+
+#undef CSONPATH_USE_PREFIX
+#include "csonpath_yyjson_const.h"
+```
+
+To use both yyjson backends (immutable and mutable) together, include the aggregator header:
+
+```c
+#include "csonpath_yyjson.h"
+```
+
+When using the mutable yyjson backend, assign the document pointer to `backend_ctx` before mutable operations:
+
+```c
+struct csonpath *mp = yyjson_mut_csonpath_new("$.a");
+mp->backend_ctx = mdoc;
+yyjson_mut_csonpath_update_or_create(mp, mroot, new_val);
+```
+
+---
+
 ## 🔌 Custom Backends
 
-csonpath is designed to be backend-agnostic. It can work with any data structure that supports array, object, and scalar semantics.
+csonpath is designed to be backend-agnostic. The C core manipulates opaque value pointers through a small set of macros, so it can work with any data structure that supports array, object, and scalar semantics.
 
-To create a custom backend, define the required macros and types in a header file (similar to `csonpath_json-c.h` or `csonpath_python.c`), then include your backend header before `csonpath.h`. This allows you to adapt csonpath for manipulating data in any format that supports array/object semantics, giving you full flexibility beyond just JSON.
+A backend is an adapter that implements those macros for a concrete value representation. To create a custom backend, define the required macros and types in a header file (similar to `csonpath_json-c.h` or `csonpath_yyjson.h`), then include your backend header before `csonpath.h`.
 
-For more details, see the existing backend implementations:
-- `csonpath_json-c.h` — json-c backend
-- `csonpath_yyjson.h` — yyjson backend
-- `csonpath_python.c` — Python backend
-- `rust/csonpath_rust_backend.h` — Rust / serde_json backend
+Existing backend adapters:
+- `csonpath_json-c.h` — json-c values
+- `csonpath_yyjson.h` — yyjson values
+- `csonpath_python.c` — Python C API values (used by the Python bindings)
+- `rust/csonpath_rust_backend.h` — Rust `serde_json::Value` (used by the Rust crate)
 
 ---
 
@@ -384,7 +438,7 @@ make tests
 | `csonpath_json-c.h` | json-c backend |
 | `csonpath_yyjson.h` | yyjson backend |
 | `csonpath_python.c` | Python C extension backend |
-| `rust/` | Rust backend (safe API, FFI, C glue) |
+| `rust/` | Rust crate and its C backend adapter |
 | `csonpath_my_fuzzing.h` | Fuzzer helpers (C) |
 | `tests/` | C and Python test suites |
 | `bench/` | Performance benchmarks |

{csonpath-0.17.0 → csonpath-0.19.0}/csonpath.egg-info/SOURCES.txt

@@ -8,7 +8,10 @@ csonpath_do.h
 csonpath_json-c.h
 csonpath_my_fuzzing.h
 csonpath_python.c
+csonpath_undef.h
 csonpath_yyjson.h
+csonpath_yyjson_const.h
+csonpath_yyjson_mut.h
 pyproject.toml
 setup.py
 csonpath.egg-info/PKG-INFO