Closed ajitid closed 3 years ago
Hmm, as far as I know, combining are not supported on https://github.com/reviewdog/errorformat
(If I 'd say), you can make wrapper-script that substitute messages as you want.
you can make wrapper-script
I'm not able to understand this. I'm using this lang server with NeoVim. Are you saying that I can pass a function to lintFormats
property? If not, where do I need to create a wrapper script and what part will call this script?
Update: I went with compact format of ESLint to solve the issue. I believe unix
format which is mentioned in the doc, while be able to parse the problems, will incorrectly report warnings as errors as no detection is applied there.
Is it possible to receive a code action or a line range fix from ESLint to nvim-lspconfig with the help of EFM Lang Server? Usually in VSCode we get a quick fix/lightbulb for rules like react-hooks/exhaustive-deps.
Unfortunately, currently, efm-langserver does not support dynamic codeAction.
Okay, thanks for the help!
Is there a reference sheet which I can use to understand and use
%f
,%l
and other formats?I am using a linter that emits message in this form:
Is there a way to parse "Warning" out of it but combine both of its sides to make the message appear as
and to tag it as a warning?
I tried
%m [%tarning/%m
but it is wrong as the second%m
overrides the first one.