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
Not sure whether this should be part of #1773 and/or #1774, but figured it's maybe just about different enough to create a separate issue.
Currently, when looking at the settings in the documentation or when going through a ruff settings file, there is no way to know which setting the rule interacts with.
Conversely, if I want to change the settings regarding a specific rule, I will almost always need to refer to that rule's documentation page to find what the rule is called. There is no logical way to deduce it without checking the documentation, unless one happens to know. (Also, there is no safeguard that the documentation for a rule is up to date with this, so can be forgotten when updating a rule as e.g. just happened here).
It would be nice if:
the settings documentation states which rule a given setting refers to
For reference, Clippy has a "Configuration" section (example) although I haven't looked at whether it's being generated automatically or not. It would be useful to have it done automatically, not sure how though.
Not sure whether this should be part of #1773 and/or #1774, but figured it's maybe just about different enough to create a separate issue.
Currently, when looking at the settings in the documentation or when going through a ruff settings file, there is no way to know which setting the rule interacts with.
Conversely, if I want to change the settings regarding a specific rule, I will almost always need to refer to that rule's documentation page to find what the rule is called. There is no logical way to deduce it without checking the documentation, unless one happens to know. (Also, there is no safeguard that the documentation for a rule is up to date with this, so can be forgotten when updating a rule as e.g. just happened here).
It would be nice if:
The text was updated successfully, but these errors were encountered: