Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for kebab-case names in error output #2041

Closed
scop opened this issue Jan 20, 2023 · 1 comment
Closed

Support for kebab-case names in error output #2041

scop opened this issue Jan 20, 2023 · 1 comment

Comments

@scop
Copy link
Contributor

scop commented Jan 20, 2023

The ability to specify noqa et al using the (now kebab-case) check names is great; they're much human friendlier than the flake8-style error codes.

Would be nice to have the error output contain those names some way, too.

This would however make the error messages longer, and simply replacing the current short check code with the long identifier before the message might push the message too far out of sight. mypy solves this by displaying the or long error identifier at the end of line in square brackets, pylint outputs the code before the message, and the long identifier at end of line in parenthesis. I suppose the pylint way would be at least more backwards compatible in ruff.

@charliermarsh
Copy link
Member

Yeah, we're planning to support kebab-case names in configuration files, noqa directives, and error outputs (probably -- details TBD). The plan is for it all to be done in a way that maintains compatibility with the existing rule code system.

I'm just gonna close this in favor of #1773 since that's the issue where we're tracking that migration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants