Fork me on GitHub
#parinfer
<
2018-01-13
>
shaunlebron00:01:13

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

shaunlebron00:01:07

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

cfleming06:01:11

@shaunlebron Sure, I have some cases noted down but haven’t had time to work up issues, sorry - I will do next week.

shaunlebron08:01:28

@cfleming np, thanks for the previous issues. super helpful

martinklepsch11:01:45

@shaunlebron parlinter looks pretty useful for editors that don’t support proper Lisp indentation

martinklepsch11:01:07

that said I find the name slightly confusing as usually the name linter is associated with some form of static analysis (maybe just me?)

dominicm17:01:14

@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.

martinklepsch19:01:36

Why not use the js version

dominicm20:01:58

The neovim js api is very ES6 and hard to wrap from cljs

dominicm20:01:11

But that's what is done now :)

shaunlebron19:01:50

@martinklepsch yeah I was afraid that would come up 😕

shaunlebron19:01:45

it was my experience at work using ESLint for javascript that it would catch a bunch of things, including formatting convention violations