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
Rubocop (a Ruby linter) can suppress lints via a magic comment in a similar way that you can #[allow(clippy::...)]. Rubocop also has a lint that triggers if one of these comments appears and is not suppressing a lint error.
One common thing I've run into is to have many #[allow(clippy::module_name_repetitions)] and then rename the module in a refactoring, which makes these properties not required and they will remain as noise.
Is such a lint feasible?
The text was updated successfully, but these errors were encountered:
Rubocop (a Ruby linter) can suppress lints via a magic comment in a similar way that you can
#[allow(clippy::...)]
. Rubocop also has a lint that triggers if one of these comments appears and is not suppressing a lint error.One common thing I've run into is to have many
#[allow(clippy::module_name_repetitions)]
and then rename the module in a refactoring, which makes these properties not required and they will remain as noise.Is such a lint feasible?
The text was updated successfully, but these errors were encountered: