You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add an optional generated report of all diagnostic information in json form. I'm thinking of something similar to the coverage report options, but tailored to any warnings/errors/notes produced by mypy (according to it's config).
Pitch
I'd like to write a problem matcher for my CI workflow(s). I could just use regex to parse stdout and go from there, but different projects have different output configurations. If I could get a comprehensive json (as verbose as possible) of all the errors/warnings/notes in json form, then I can adequately match the diagnostic info to exact places in the source code.
I imagine a single warning would look like:
[
{
"severity": "error",
"line": 92,
"column": 29,
"path": "clang_autodoc/clang_parse.py",
"symbol": "arg-type",
"message": "Argument 1 to 'serialize_src_loc' of 'ClangParse' has incompatible type 'int'; expected 'SourceLocation'"
}
]
FWIW, pylint has a similar CLI option:
pylint --output=json:somefile.json srcs/*.py
The text was updated successfully, but these errors were encountered:
Feature
Add an optional generated report of all diagnostic information in json form. I'm thinking of something similar to the coverage report options, but tailored to any warnings/errors/notes produced by mypy (according to it's config).
Pitch
I'd like to write a problem matcher for my CI workflow(s). I could just use regex to parse stdout and go from there, but different projects have different output configurations. If I could get a comprehensive json (as verbose as possible) of all the errors/warnings/notes in json form, then I can adequately match the diagnostic info to exact places in the source code.
I imagine a single warning would look like:
FWIW, pylint has a similar CLI option:
The text was updated successfully, but these errors were encountered: