Closed cideM closed 5 years ago
The information might be included in the JSON above there somewhere.
I updated the initial post with the entire output of ALEInfo
I looked at the source code for the flow.vim
file and even though I have no experience in vim scripting it seems like Ale simply does not parse the extra
field. It parses for l:error in get(l:flow_output, 'errors', [])
and then for l:message in l:error.message
but the details I am missing are in error.extra.message
not error.message
.
Update
I looked at the VSC flow plugin and it contains types for the old error format and the new format. So bottom line: vim.flow
just needs to be updated.
I might take a shot at a PR although considering my lack of expertise in all things (neo)vim internals we'll see how it goes.
Probably true.
I created a fork with the added functionality in a commit. I am going to play around with it a bit, before a PR, as I can't find a lot of documentation on how flow reports errors.
Okay, sounds good.
This issue was never closed but it was fixed by https://github.com/w0rp/ale/pull/946
Thank you for closing this.
Not sure if this is an issue with
vim-flow
orale
. In e.g., Visual Studio Code I see more detailed error messages. Running:ALEDetail
in neovim does not help. This is what I see in neovim:Here is VSC:
And here is
ALEInfo
:Pretty JSON