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
I think local imports (i.e. those not in the file header) are most often added manually and for good reasons (e.g. to select a more appropriate typeclass instance). Unfortunately, your plugin removes such imports if IDEA (wrongly) deems them unused. I’m ok with removing auto-generated stuff, but removing a shadowing typeclass instance will be unnoticed and can lead to crashing code. Maybe it’s a good idea not to remove local imports, what do you think?
The text was updated successfully, but these errors were encountered:
Ouch, I didn't know that IntelliJ's import optimizer looked at local imports (my stuff certainly ignores them). Since I just use IntelliJ's stuff to identify and remove unused imports, I'm not sure it'll be possible to fix this issue from my side. Ideally IDEA would be patched to not deem these imports unused, or their optimizer would have an option to leave local imports untouched.
In the meantime, I guess the only solution is to turn off removing unused imports from this plugin's settings if you run into this problem.
I think local imports (i.e. those not in the file header) are most often added manually and for good reasons (e.g. to select a more appropriate typeclass instance). Unfortunately, your plugin removes such imports if IDEA (wrongly) deems them unused. I’m ok with removing auto-generated stuff, but removing a shadowing typeclass instance will be unnoticed and can lead to crashing code. Maybe it’s a good idea not to remove local imports, what do you think?
The text was updated successfully, but these errors were encountered: