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
This might be somewhat similar to some existing issues so if it would be preferable to comment on one of them and close this one that's fine, but I didn't see it specifically.
I have some automatically generated code which triggers the single_component_path_imports lint. I'm not opposed to the lint in general, but I'd rather keep the automatically generated code unedited by hand. I thought I could just add the allow(...) attribute to the module declaration, but it doesn't seem to apply recursively to the code in the declared module.
Reproducer
I tried this code:
#[allow(unused_imports)]#[allow(clippy::single_component_path_imports)]mod test {use anyhow;}
I expected to see this happen: The lint would be suppressed.
Instead, this happened: The lint warning continues to appear.
Summary
This might be somewhat similar to some existing issues so if it would be preferable to comment on one of them and close this one that's fine, but I didn't see it specifically.
I have some automatically generated code which triggers the
single_component_path_imports
lint. I'm not opposed to the lint in general, but I'd rather keep the automatically generated code unedited by hand. I thought I could just add the allow(...) attribute to the module declaration, but it doesn't seem to apply recursively to the code in the declared module.Reproducer
I tried this code:
I expected to see this happen: The lint would be suppressed.
Instead, this happened: The lint warning continues to appear.
Version
Additional Labels
No response
The text was updated successfully, but these errors were encountered: