This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-04-23
Channels
- # aws-lambda (1)
- # bangalore-clj (13)
- # beginners (12)
- # boot (3)
- # cider (1)
- # cljs-dev (20)
- # clojure (208)
- # clojure-finland (1)
- # clojure-france (1)
- # clojure-russia (30)
- # clojure-serbia (12)
- # clojure-spec (7)
- # clojure-uk (14)
- # clojurescript (16)
- # cursive (6)
- # datomic (10)
- # emacs (1)
- # hoplon (4)
- # keechma (14)
- # leiningen (2)
- # off-topic (6)
- # om (43)
- # onyx (32)
- # pedestal (8)
- # perun (2)
- # re-frame (7)
- # reagent (33)
- # specter (5)
- # vim (4)
- # yada (9)
Currently rewriting lein-bikeshed. Almost at a point where it can work on stdin, which is awesome 🙂
It's interesting how different use cases (and opinions about api design) completely change the way you design a library.
It's fine for lein-bikeshed to work how it does because: - It runs in it's own JVM so has a snapshot of "state" - It's output format is only for human reading - Only used from lein position Throw a REPL at it and now you want to: - Finely control the files it lints - Use a standard formatting output that is easy for tooling to read - Potentially pass in a string to lint instead of using the current state of the repl