> On Sep 30, 2018, at 23:41, Alan Thompson wrote:
>
> It is easy to overdo it when trying to predict future needs. I always (now)
> do the minimal solution, with the expectation that it *may* evolve in the
> future.
Normally I'd agree: YAGNI is great for functionality that can be added with
I'd prefer an option map over kwargs in general, and I wouldn't namespace
the options because they're not something that I'd expect to stick around.
(fetch url {:timeout 10})
Regarding the output, if it's a Ring response map, I'd be inclined to leave
the keywords bare for compatibility. If it's n
Lacinia is an open-source implementation of Facebook's GraphQL
specification, in Clojure.
GraphQL is an outstanding approach to getting diverse clients and servers
exchanging data cleanly and efficiently.
GitHub repo: https://github.com/walmartlabs/lacinia
Documentation: http://lacinia.readthed
https://github.com/jkk/honeysql
SQL as Clojure data structures. Build queries programmatically -- even at
runtime -- without having to bash strings together.
This is a bug fix release:
* #sql/inline nil should produce NULL. Fix #221. (@seancorfield)
* #sql/inline :kw should produce "kw"
