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
The output when a line is reported uses the @ character to separate the filename from the line number, e.g:
path/to/some/module.py@91:12 An error is at this location.
This differs from most other tools, which use a colon. The colon syntax is understood by many other tools that parse output (e.g. mypy-json-report) and the file finder in most editors (e.g. VS Code). e.g:
path/to/some/module.py:91:12 An error is at this location.
Would the maintainers be open to changing the output format to be the same as other tools? It would (imo) make fixit output much easier to work with.
The text was updated successfully, but these errors were encountered:
The output when a line is reported uses the
@
character to separate the filename from the line number, e.g:This differs from most other tools, which use a colon. The colon syntax is understood by many other tools that parse output (e.g.
mypy-json-report
) and the file finder in most editors (e.g. VS Code). e.g:Would the maintainers be open to changing the output format to be the same as other tools? It would (imo) make fixit output much easier to work with.
The text was updated successfully, but these errors were encountered: