-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
importsNotUsedAsValues is wrong #1094
Comments
@kdy1 What if I don't remove the option, but disassociate it with any behaviour for now? The behaviour it's currently associated with should unconditionally be "remove". |
I think it's not correct. I think it should at least panic if an option which causes wrong behavior is provided. |
@kdy1 Nevermind, I can fix it to cause the correct behaviour. |
@nayeemrmn Sounds great! |
This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
@kdy1 This is not the behaviour of
tsc
under"importsNotUsedAsValues": "preserve"
. The correct behaviour is to never preserve completely unused import identifiers. The above branch should always be used.I think
ImportNotUsedAsValues
should be removed since it's a misunderstanding of the equivalenttsc
option.Originally posted by @nayeemrmn in #1060 (comment)
It's a breaking change.
The text was updated successfully, but these errors were encountered: