microsoft / microsoft/TypeScript
Command clicking FC's in react doesn't work anymore.
Open
Nobody has claimed this yet.
Needs More Info
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.4k
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 117
Description
Does this issue occur when all extensions are disabled?: Yes/No
- VS Code Version: 1.87.2
- OS Version: macOS 14.1.1
Steps to Reproduce:
- Open a react project with functional components
- CMD Click a functional component from your code
- It doesn't open the component. It opens the definition for
FCin react
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue in VS Code 1.87.2 on macOS 14.1.1 using a React project with functional components, then inspect the command-click definition-navigation path. Done means command-clicking a functional component opens that component rather than React's FC definition; the payload names no source file or test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100