4 ms·

Thanks a ton for the feedback! You're right maybe the wording is wrong: query more than manipulate. By the way, querying like jq might be an interesting new fe

Thanks a ton for the feedback! You're right maybe the wording is wrong: query more than manipulate. By the way, querying like jq might be an interesting new feature. Don't know exactly in which direction it should go / what it should do / how exactly it should look like (grammar) N.B.: I have another project called jql which is actually a simpler - and faster - jq made with Rust https://github.com/yamafaktory/jql https://github.com/yamafaktory/jql

johnsonjo 6y ago
Wow that’s awesome you actually have a jq like implementation. Hmmm since it’s a graph maybe you could go with something like openCypher [0] or GQL [1] (possibly gremlin too) or maybe you could even query it with GraphQL (although GraphQL only traverses down in a tree fashion)? Although some sort of simpler jq like syntax might be able to make more sense. It would need to be able to branch out somehow. I think even an emmet [2] like syntax might work well. [0]: http://www.jcc.com/resources/jcc-blogs-menu/blog-database-dreams/122-property-graph-standards-update-july-2020 http://www.jcc.com/resources/jcc-blogs-menu/blog-database-dr... [1]: https://www.gqlstandards.org/gql-blogs https://www.gqlstandards.org/gql-blogs [2]: https://docs.emmet.io/cheat-sheet/ https://docs.emmet.io/cheat-sheet/