fix(extract): recognize uppercase TypeScript extensions#1881
Closed
xkam7ar wants to merge 1 commit into
Closed
Conversation
safishamsi
added a commit
that referenced
this pull request
Jul 14, 2026
…section Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Collaborator
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Normalize a file suffix once before grammar selection so uppercase TypeScript-family extensions (
.TS,.TSX,.MTS, and.CTS) use the same TypeScript grammars as their lowercase forms.Previously,
extract_js()recognized uppercase JavaScript extensions through a lowercase check but compared the TypeScript branches against the original case-sensitive suffix. TypeScript-only declarations could therefore be omitted.Tests
.TSgraphify update .: passed with no tracked generated changesgit diff --check: passed