-
Notifications
You must be signed in to change notification settings - Fork 506
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
Import alias flagged as unused import #526
Comments
@gabrielittner this is a regression in 0.34.0? |
Yes. 0.33 was working without this issue on the same code |
@gabrielittner could you provide a more complete code snippet? it looks like the rule attempts to handle import aliases (and tests that have import aliases are passing), so I want to understand what broke. |
I will try to put together something reproducible tomorrow |
@gabrielittner I'm going to revert the changes to the unused imports rule that we made in 0.34.0, and I suspect it will fix your issue, but when you have a repro case let me know and I can test. |
@gabrielittner if you can provide your repro case, #535 is attempting to fix the regressions in 0.34.0, so we want to make sure your case is covered. |
i also have this case. |
Similar example was provided in the PR review. It has been added as a test case and fixed now. |
Fixed via #535 |
Something like
import a.b.c.MyClass as SomeOtherName
is marked as an unused import after upgrading to 0.34.0.The text was updated successfully, but these errors were encountered: