Clojurians Log v2

Hi HyperFiddle. Is the idea here to give the user (end customer) a flexible way to query there data? I ask because it seems similar to an idea I have been bouncing around in my head. The idea is that there is an impedance mismatch between using http calls and fulfilling the users request. This is a bit hard to explain, so here is an example: What should the call /people?age=5 return? I would assume it would be “all people with an age of 5”. But how would you return everyone under the age of five? What would be the QueryParm? I’m somewhat novice in this regard, but trying to push all information into a path param, or query param seems arbitrary. I would rather front end clients and/or end users have more freedom to get there information. For example, a client could send a SQL expression (or datomic query) and if it was vetted (authorization and authentication) the request would be fullfilled. The main concerns I have heard seem to around security and performance, but nothing that makes the idea itself impossible. But possible it makes it impractical? I’m bringing this up, because it sounds very similar to the main description on hyerfiddle: > It connects directly to any Datomic database. It’s extensible in Clojure, which means you can use it to make scrappy CRUD apps.

I guess its odd that there is such an emphasis on small re-usable components at the PL level, but at a systems level were so much more limited.

Drewverlee, Yes. that’s a great question, if I understand it right. I did my best to draw how Hyperfiddle fills query parameters. This is by far the worst part of our UI and its on the roadmap to simplify it.

@dustingetz uploaded a file: https://clojurians.slack.com/files/U09K620SG/F8RH1NNQ3/image.png

@drewverlee

Thanks @dustingetz i’ll have to dig into this when i get home.