Skip to content

Print errors in more standard format so editors and other tools can better automatically parse them #373

@lolpack

Description

@lolpack

Describe the Bug

pyrefly errors CLI does not fit the fairly universal "error in file" format that mypy or gcc or most Linux toolchains use, which is a line like /home/rec/git-typing/pytorch/torch/_inductor/lowering.py:366:36-51, without any prefix like ERROR .

That specifically excludes emacs and quite possibly other vi-family editors. (The net result is that in emacs, I can't click on your errors to go to the file and line.)

cc @rec

Sandbox Link

No response

(Only applicable for extension issues) IDE Information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    UserBugs reported by external users that should be prioritisedcodenavenhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions