JS: Various TypeScript extraction fixes. #15072
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
And add a new
SEMMLE_TYPESCRIPT_SKIP_EXTRACTING_TYPES
environment variable to skip extraction of all types.This is a workaround for an internal report about long extraction times.
I'm not sure why those fixes weren't needed previously, and I couldn't replicate them when running tests.
They're clearly basic TypeScript errors, so I'm not sure what's going on.
I think it's something for @asgerf to look at when he's back?
I tried the new flag locally on
microsoft/vscode
.The extraction got faster, and we only lost a single alert on that project.
And extraction is way faster with the flag on a minimal example from the internal report.
Evaluation were very uneventful (nightly-old.yml, typescript-full.yml)