devBaunz

Works just fine, assuming the following tweaks made: metro.config.js ```js const { getDefaultConfig, mergeConfig } = require("@react-native/metro-config"); const path = require("path"); /** * Metro configuration * https://reactnative.dev/docs/metro * Tweaks by...

@ephraimfeldblum Sure thing, sorry about it - was actually copy-pasting from my local fork (which pre-dates the macro usage) so didnt check it in-depth. I'll get to it today -...

@LiorKogan sure, any specific files/location preferred ? For now here's a couple of examples: ``` JSON.SET user1 $ '{"name":"Alice","member":"test","age":25}' JSON.SET user2 $ '{"name":"Bob","member":"other","age":30}' JSON.SET user3 $ '{"name":"Carol","member":"test","age":22}' # Filter where...

Firstly let me say THANKS for the quick replies, highly appriciated. And 100% agreed with `FILTER` and `MFILTER` variants, I currently only implemented a `MGET` variant since it has the...

It's true that chaining filters is nice conceptually, and JsonPath already support the basic case, just very ugly syntax, like you can filter from root such as `[? ($.age >...

> @LiorKogan Consider having position of keys which are easier to define (from first pos till the end), such as > > JSON.FILTER < path > < filter-expression > key1...

thanks all, I'll get a more detailed implementation done at the PR for a `JSON.FILTER` and `JSON.MFILTER` then we can move discussion into PR for a more in-depth changes/requests

@LiorKogan @oshadmi @ephraimfeldblum just heads up - while working on testing and checking the code variants I actually came across a very annoying issue with the `JSON.FILTER` variant as it...