This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-01-13
Channels
- # beginners (99)
- # boot (2)
- # boot-dev (4)
- # chestnut (2)
- # cider (75)
- # clara (43)
- # cljs-dev (1)
- # cljsjs (6)
- # cljsrn (4)
- # clojars (2)
- # clojure (76)
- # clojure-brasil (1)
- # clojure-france (1)
- # clojure-italy (2)
- # clojure-spec (30)
- # clojure-uk (4)
- # clojurescript (39)
- # core-async (1)
- # core-logic (2)
- # cursive (1)
- # data-science (7)
- # datomic (14)
- # docker (12)
- # emacs (6)
- # fulcro (69)
- # garden (4)
- # hoplon (7)
- # jobs-discuss (46)
- # leiningen (3)
- # lumo (3)
- # off-topic (12)
- # om (2)
- # parinfer (12)
- # perun (9)
- # re-frame (44)
- # reagent (6)
- # rum (1)
- # shadow-cljs (73)
- # specter (5)
- # unrepl (10)
- # vim (2)
✅ i got markdown test cases for all the known bugs. gonna sleep on this and cut a release tomorrow: https://github.com/shaunlebron/parinfer/pull/181
I know there’s more behavior to fix, but I’d like to get the bug fixes rolled out and close out all those issues. will start fresh on the new behavior problems when found
@shaunlebron Sure, I have some cases noted down but haven’t had time to work up issues, sorry - I will do next week.
@cfleming np, thanks for the previous issues. super helpful
@shaunlebron parlinter looks pretty useful for editors that don’t support proper Lisp indentation
that said I find the name slightly confusing as usually the name linter is associated with some form of static analysis (maybe just me?)
@cfleming did you ever open source your parinfer implementation? I'm interested in seeing how well a JVM version of parinfer would integrate into neovim.
Why not use the js version
@martinklepsch yeah I was afraid that would come up 😕
it was my experience at work using ESLint for javascript that it would catch a bunch of things, including formatting convention violations