-
Notifications
You must be signed in to change notification settings - Fork 44
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
Elusive breakage of Add all missing imports
source action. Needs further investigation.
#134
Comments
|
What about the current release, v5.7.20241021? |
|
hmm, i made the mistake of not cloning the current state of my project in which this issue occurred, and now i can't reproduce it. well, next time i run into the problem again (this is NOT a single instance. it has happened to me in other projects), i will try to remember to freeze it |
Add all missing imports
Source ActionAdd all missing imports
source action. Needs further investigation.
looking back, i didn't perform as thorough an investigation as i should have. if i run into the same behavior again, i'll try to remember to push a repro and test it on a clean os installation. i'll close this for now as not reproducible |
yay, the problem is happening again, i'll freeze this project and try to create a minimal reproduction. stay tuned |
it's hard to explain to non-windows users what Windows Sandbox is and how it's almost literally a "brand-new installation of Windows"[1], so there are no user settings or configurations whatsoever. this is a brand-new installation of vscode with no settings or configurations whatsoever. |
oh right, i almost forgot the most important part: tsconfig.json {
"compilerOptions": {
"verbatimModuleSyntax": true
}
} this bug only happens when this property is enabled |
The
JavaScript and TypeScript Nightly
v5.7.20240911
update broke some part of theAdd all missing imports
source action. Ever since then, some imports would be incorrectly imported with thetype
only attribute; i.e.instead of
for situations where type only imports are not correct.
The text was updated successfully, but these errors were encountered: