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 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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: