vscode 2018-05-11

I noticed. That would be a bit hard to implement though? Custom macros, for instance. I wonder if it is possible to dynamically add to the grammar…

So is it a known thing that intellisense isn't working for macros?

A grammar based method will never work

Referring to requiring a macro

What do you mean intellisense not working?

When typing out a macro to refer it won't show up

Only functions do

[compojure.core :refer [defrou

defroutes doesn't show in the list

or any other macro in that namespace

Also joker just updated and linting seems to be broken now

Care to report that issue to the repo? (About intellisense and macros).

The joker issue too, if you have the time. Hopefully that one is easy to fix.

I don't know where the error is though

Just that I am on commuting foot and would like to be reminded of this when I get home. So just a place holder.

right, i'm just saying

Oddly enough I don't see why the new Joker would break anything. There aren't any significant changes

Too bad, might be a bit tricky to fix then.

TypeError: Cannot read property 'getDocument' of undefined
	at Object.lintDocument$$module$calva$repl$middleware$lint [as lintDocument]

I'm looking at the JS and I don't see what's wrong

I wonder if it could even be due to the Joker update?

That was a guess

We will have a look. Hopefully not too hard to fix.

Debugging is impossible since the dist js is minified garbage

Debugging is a bit painful with the development code as well. Because we have started to port it to Clojurescript and the source maps don't quite cut it.

But please feel invited to fork and see if it gets clearer. If you do you need to Run Build Task... after npm install.

I'm looking at the code, but I have never written or know how VSCode extensions work

Calva was my first experience with it, so I am no expert. But they (the vscode team) has made it reasonable easy. When the build task is running, press F5 and it will launch a new window (called the Extension Host) with the dev extension active

Before we started to port things to Clojurescript it was easy to put breakpoints and debug things.

My VSCode was a version behind so seeing if that helps

Didn't change anything as expected

@maxt has joined the channel

Thanks for the reference

We still have the inherent issue that there is no grammatical difference between a macro call and a function call.

If you notice, there is no macro keyword in that cson.