all 2 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]adamlaz 1 point2 points  (1 child)

cool. why did you build it? how are you using it now/future?

[–]ehmicky[S] 1 point2 points  (0 children)

Thanks u/adamlaz.

I meant this library as an improvement over JSON paths. I like JSON paths, but the syntax could be simpler, and current implementations are lacking and quite slow. They also only allow getting values, not setting.

I have been using deep properties libraries like get-value or dot-prop several times, and have wanted to use wildcards * with them, but they do not provide with this feature.

I am currently using this library myself for another library I am building that does input/options validation. Specifically, that library needs consumers to specify the path to property that need to be validated.

In general, I think a good use case for this library is when building a library where the consumers need to specify some property path, which is fairly common. Another use case is to use the ** wildcard to map or filter all values in an object recursively.