JS: Extract TS snippets with no tsconfig.json file

[asgerf]

Fixes #18801

This fixes the bug that was supposed to be fixed in #18550, but that PR only fixed it in the legacy entry-point used by qltest. Meaning it worked in tests but not in production 🤦. This PR uses the same fix in AutoBuild entry point. We should unify the two entry points ASAP but for now this PR just fixes the bug.

[Copilot]

PR Overview

This PR fixes a bug where TypeScript snippets were not being extracted in production due to a missing tsconfig.json, by applying the same fix previously used for qltest to the AutoBuild entry point.

• Adds extraction logic for TypeScript snippets from state.getSnippets()
• Ensures that remaining TypeScript files include snippets that haven’t been extracted
• Maintains the existing file ordering and extraction process

Changes

File	Description
javascript/extractor/src/com/semmle/js/extractor/AutoBuild.java	Added a loop to iterate over TS snippets and add them to the extraction queue if not already processed

Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (2)

javascript/extractor/src/com/semmle/js/extractor/AutoBuild.java:1092

• Verify that FileType is implemented as an enum; if it is not, consider using .equals() instead of '==' to ensure proper comparison.

&& FileType.forFileExtension(entry.getKey().toFile()) == FileType.TYPESCRIPT) {

javascript/extractor/src/com/semmle/js/extractor/AutoBuild.java:1090

• [nitpick] Consider renaming 'entry' to a more descriptive name such as 'snippetEntry' to improve code clarity.

for (Map.Entry<Path, FileSnippet> entry : state.getSnippets().entrySet()) {

Tip: Copilot only keeps its highest confidence comments to reduce noise and keep you focused. Learn more

[erik-krogh]

👍

We should unify the two entry points

I assume you have that on some list of yours?

[asgerf]

I assume you have that on some list of yours?

I've created an issue for it as I couldn't find one.

[asgerf]

Re-running DCA as performance numbers were unexpected and suspicious

[asgerf]

Evaluation looks good now.