Show HN: JAQT – JavaScript Queries and Transformations

(github.com)

100 points by Poefke 4 days ago

39 comments

View on Hacker News

Hi all,

I've made a javascript library to simplify searching/sorting/filtering in arrays of objects. Its inspired by both GraphQL and SQL, but implemented using javascript Proxies. Instead of creating a new language, its all just javascript.

I've made it as part of an experimental database, which uses javascript as the query engine. The normal javascript map/reduce/sort functions are quite difficult to master for junior developers. JAQT is easier to explain, and can still be used in combination with any existing array functions.

Please let me know what you think of the API and its ease of use!

jansommer 4 days ago

Wouldn't the query for your example just be

data.filter(d => d.friends.includes("John")).map(d => ({name: d.name+" "+d.lastName}))

Maybe I'm missing the bigger picture, but that doesn't seem so bad

Reply View 16 replies
  • allannienhuis 4 days ago

    one of the cases something like this is useful for is when you have user configured saved 'filters' - you can simply pass the stored object into the where clause. I agree if you're doing hard-coded queries on arrays of objects, this may not add a lot. That said, a consistent syntax for doing searches and mapping is useful - projects like lodash have that as part of their api too.

    Reply View 2 replies
  • meiraleal 4 days ago

    I liked JAQT API but it is not really good to create a layer on top of already simple functional constructors.

    Reply View 11 replies
    • austin-cheney 4 days ago

      Why is that not good? JavaScript is full of layers of unnecessary abstraction often for completely superficial reasons and sometimes even irrationally applied at great cost in defiance of evidence and simplicity. So, what makes this specific example less good than all the other countless examples of abstractions most JavaScript developers would happily die to defend?

      Reply View 10 replies
      • meiraleal 4 days ago

        because in the past it didn't have those functional constructors so things like underscore or lodash would be needed but adding a layer as you mentioned. It is not good, for me, to add a dependency for this again. But in the end I have in my utils file a few functions that basically do what JAQT does and I might copy a few more.

        Reply View 9 replies
  • Poefke 3 days ago

    Author here, if you are comfortable with filter/map/reduce, than JAQT doesn't provide much benefits, I agree. My target audience is developers who aren't that used to that. I've had much more success with junior developers using JAQT, then trying to get them to use map/reduce.

    Reply View 0 replies
drawkbox 3 days ago

I like that it mimics SQL queries/filtering which is straightforward.

Typically I use something like JSONPath [1] (basically XPath for JSON) [2] or jq for this but having more options with other syntax and style is helpful.

For streamed JSON like NDJSON [3] there are some nice filtering options [4]

[1] https://en.wikipedia.org/wiki/JSONPath

[2] https://datatracker.ietf.org/doc/html/rfc9535

[3] https://github.com/ndjson/ndjson-spec

[4] https://github.com/mbostock/ndjson-cli?tab=readme-ov-file#fi...

Reply View 0 replies
ssahoo 4 days ago

Looks like .net Linq. Many js projects use lodash and variants, how do you compare that?

Reply View 1 reply
  • Poefke 3 days ago

    LINQ is much more sophisticated, translating as much of the query as possible to the target (server) language, like SQL. JAQT is not doing that. lodash, underscore, and others, had a great impact on javascript by introducing lots of functional paradigms. Most of that is now part of javascript itself. JAQT's main purpose is to allow you to filter arrays of objects and create custom objects, just like GraphQL. And be a bit easier to learn than Array.map/reduce/filter.

    Reply View 0 replies
csbbbb 3 days ago

With JSON, sometimes you just need a fluent, permissive way to query objects that you don't already know a type structure for. This seems useful! I love JSONata for exploring json data, but it's more useful for static analysis than programming.

Reply View 0 replies
[removed] 4 days ago
[deleted]
Reply View 0 replies
gryzzly 4 days ago

can a query like that be observable? so updating the array/object would cause the results to update?

Reply View 3 replies
  • af3d 4 days ago

    AFAICT this library generates "flat" JSON objects. Wouldn't be too hard to implement it such that references to Javascript objects are instead returned, where some sort of callback could be invoked whenever the actual object is modified. I do rather like this "query engine" approach, too. It's a much cleaner interface IMO and doesn't seem to incur too much overhead either....

    Reply View 0 replies
  • jansommer 4 days ago

    I don't know if RxJS has run out of fashion, but that would give you observable js using map/filter/reduce etc.

    Reply View 0 replies
porker 4 days ago

In a similar vein is https://pbeshai.github.io/tidy/ which I've used for 3+ years. It's a really nice lightweight transformer.

I've also used https://github.com/uwdata/arquero once (better performance for large datasets).

Reply View 2 replies
  • pdyc 4 days ago

    any idea what does tidy uses internally? or is it iterating over entire array for every operation?

    Reply View 0 replies
  • [removed] 4 days ago
    [deleted]
    Reply View 0 replies