-
Notifications
You must be signed in to change notification settings - Fork 944
Fix assertion violation in auto-imports for JSX tag when React is type-imported #3650
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
Open
Copilot
wants to merge
8
commits into
main
Choose a base branch
from
copilot/fix-jsx-tag-import-issues
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+141
−19
Open
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
f1fedab
Initial plan
Copilot bad0098
fix: handle multiple symbol names in type-only import promotion for J…
Copilot 8134793
simplify type-only promotion to only return promotion fixes, no auto-…
Copilot cfe5f6c
fix: suppress silly duplicate import, add both-type-only edge case test
Copilot 32a7b79
refactor: getSymbolNamesToImport returns richer info with isTypeOnly …
Copilot 4fa2ea3
disambiguate type-only promotion fixes via error message string matching
Copilot 1df3b45
fix: fall back to all type-only fixes when message filter matches none
Copilot 6e3541d
refactor: consolidate disambiguation comment at filtering site
Copilot File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
75 changes: 75 additions & 0 deletions
75
internal/fourslash/tests/codeFixPromoteTypeOnlyImportJsxTag_test.go
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,75 @@ | ||
| package fourslash_test | ||
|
|
||
| import ( | ||
| "testing" | ||
|
|
||
| "github.com/microsoft/typescript-go/internal/fourslash" | ||
| "github.com/microsoft/typescript-go/internal/testutil" | ||
| ) | ||
|
|
||
| // Test that auto-imports for JSX tags don't crash when React is type-imported. | ||
| // When both the JSX namespace (React) and the component need to be imported, | ||
| // getSymbolNamesToImport returns multiple names and the type-only promotion | ||
| // path should handle this gracefully instead of panicking. | ||
| func TestCodeFixPromoteTypeOnlyImportJsxTag(t *testing.T) { | ||
| t.Parallel() | ||
| defer testutil.RecoverAndFail(t, "Panic on fourslash test") | ||
| const content = `// @module: preserve | ||
| // @verbatimModuleSyntax: true | ||
| // @jsx: react | ||
| // @Filename: /react.ts | ||
| const React: any = {}; | ||
| export default React; | ||
| // @Filename: /bar.tsx | ||
| import type React from "./react"; | ||
|
|
||
| <Foo/**/ />;` | ||
| f, done := fourslash.NewFourslash(t, nil /*capabilities*/, content) | ||
| defer done() | ||
| f.GoToMarker(t, "") | ||
| // The fix should promote the type-only import of React to a regular import. | ||
| // The "Cannot find name 'Foo'" error does not produce an auto-import for | ||
| // React since it's already imported (as type-only, handled by promotion). | ||
| f.VerifyImportFixAtPosition(t, []string{ | ||
| `import React from "./react"; | ||
|
|
||
| <Foo />;`, | ||
| }, nil /*preferences*/) | ||
| } | ||
|
|
||
| // Test edge case where both the component name (Foo) and the JSX namespace (React) | ||
| // are type-only imported. Each diagnostic is matched to its symbol via the error | ||
| // message, so each produces only its own promotion fix (no duplicates). | ||
| func TestCodeFixPromoteTypeOnlyImportJsxTagBothTypeOnly(t *testing.T) { | ||
| t.Parallel() | ||
| defer testutil.RecoverAndFail(t, "Panic on fourslash test") | ||
| const content = `// @module: preserve | ||
| // @verbatimModuleSyntax: true | ||
| // @jsx: react | ||
| // @Filename: /react.ts | ||
| const React: any = {}; | ||
| export default React; | ||
| // @Filename: /foo.ts | ||
| export function Foo() { return null; } | ||
| // @Filename: /bar.tsx | ||
| import type React from "./react"; | ||
| import type { Foo } from "./foo"; | ||
|
|
||
| <Foo/**/ />;` | ||
| f, done := fourslash.NewFourslash(t, nil /*capabilities*/, content) | ||
| defer done() | ||
| f.GoToMarker(t, "") | ||
| // Both Foo and React are type-only imported. The error message string | ||
| // matching disambiguates which diagnostic is about which symbol, so each | ||
| // diagnostic produces only its own promotion fix (no duplicates). | ||
| f.VerifyImportFixAtPosition(t, []string{ | ||
| `import type React from "./react"; | ||
| import { Foo } from "./foo"; | ||
|
|
||
| <Foo />;`, | ||
| `import React from "./react"; | ||
| import type { Foo } from "./foo"; | ||
|
|
||
| <Foo />;`, | ||
| }, nil /*preferences*/) | ||
| } |
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
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.
Uh oh!
There was an error while loading. Please reload this page.