Fork me on GitHub
#clojure-uk
<
2020-08-11
>
dharrigan07:08:19

Good Morning!

djm07:08:49

👋

Jakob Durstberger07:08:37

Morning 🙂

dharrigan09:08:57

I really do enjoy using the cognitect aws library

dharrigan09:08:08

easy to use 🙂

dominicm12:08:36

I thought the lack of functions would be an annoyance tbh. I'd love to know the rationale in the fullest.

rickmoynihan12:08:44

I’ve used the lib myself, it is really good, and there are definite benefits to the design; but yes the lack of functions were a bit annoying. I found you had to use the repl doc functions a lot to inspect the docs, rather than just being able to browse them

dominicm12:08:53

Right, I guess it's optimized for a repl workflow, rather than a cider/tooling one.

rickmoynihan12:08:46

well they’ve invented their own way of accessing docs — mostly driven by spec; which is fine… but unfortunately specs doc story isn’t great at the minute.

Ben Hammond12:08:41

didn't they just try to be as thin a wrapper as possible

Ben Hammond12:08:59

that way when AWS change the js specs

Ben Hammond12:08:15

they still work (as much as possible)

rickmoynihan12:08:58

I do sometimes wish clojure had better doc tooling for APIs etc. There are a bunch of things that don’t have a native uniform way to document in particular namespaced keywords and specs, but also a few other things that might at times be handy… - deftypes/records - defmethod implementations (contributing docs to the defmulti) Admittedly the later ones are perhaps a bit more controversial but would at times I think be useful. Though hard to know how they’d implement docs for deftypes/records; and the work arounds are sufficient.

dominicm12:08:09

I suppose you don't get a compiler error, you get something else instead?

rickmoynihan12:08:26

yeah you essentially get a spec error iirc