Spec Editor integration
PilchardFriendly opened this issue · 3 comments
Hi - I'm using spec inside VSCode via spago. I'm very happy with how its worked so far.
My "micro-movements" are now from 'failing test output' to 'test' to 'source code'.
For this, I was thinking of trying to add the failing test location (file/linenumber) to some json that an extension in VSCode could parse.
Maybe you've seen something that can do this?
As a start, I don't think line-number/filename are preserved in the Spec Tree. What would it take to make that available as meta-data on the spec and input into the reporter?
Note - I've done a quick look to see if purescript even supports LineNumber elaboration - and the closest I can see is this:
I think these errors are about line numbers in the Haskell code that the compiler is written in. What you are trying to accomplish might be better served with sourcemaps.
@PilchardFriendly I'm also interested in this and I know others has too.
This would make the testing feature in the Intellij plugin more usable as well. Right now i was thinking of traversion the ast when a test fails to find it. but it would be much better if the line information where accessible for reporters to use