linter output format is not standardized about cspell HOT 7 CLOSED

With 3.1.1, this should work as expected.

I tested it with iTerm2, cmd-click will open the expected file and take the cursor to the right location.

I'm going to close for now.

from cspell.

Thank you for pointing that out.

from cspell.

@ssbarnea I ran into the same issue.

Until there is a fix you can pipe the output to sed to replace characters to make it work in iTerm2:

cspell --config './.vscode/cSpell.json' 'src/**/*.*' | sed "s/^/\.\//" | sed "s/\[/:/" | sed "s/\, /:/" | sed "s/\]//"

There's probably a more elegant pipe/sed command to use, but I didn't have the patients to figure it out 😉

from cspell.

@ssbarnea and @cdeutsch where would I find an example of "standard" format of linters? Just trying out a few linters, I get very different output.

from cspell.

Examples:

stylelint:

eslint:

tslint:

from cspell.

I do not yet have such a database but I plan to build one in the future.

One thing I can guarantee to be the safest approach: user path:line:column format as 9/10 linters can support this format and is known to work with most consumers, most of them even accept "cmd file:line:colum" format for opening the file at the right line/column, so no need to parse it.

from cspell.

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

from cspell.