Repository navigation
VSCode thinks there are 2 definitions of a React Component #51459
Description
VSCode thinks there are 2 definitions of a React Component
This issue was brought up recently but without sufficient info. Here is a minimal reproduction example:
- VSCode Version: 1.24.0
- OS Version: MacOS High Sierra 10.13.4 (17E202)
Steps to Reproduce:
- Create a React app
$ create-react-app my-bug-example
$ code my-bug-example- Change src/App.js to
import React, { Component } from 'react';
class App extends Component {
render() {
return (
<div className="App">
<MyComponent />
</div>
);
}
}
export default App;
class MyComponent extends Component {
render(){
return <MySingleComponent text="Instance 1" />
}
}
class MySingleComponent extends Component {
render(){
return <p>{text}</p>
}
}
- CMD + hover on
<MySingleComponent text="Instance 1" />
- CMD + click on
<MySingleComponent text="Instance 1" />
Does this issue occur when all extensions are disabled?: Yes
Activity
vscodebot commentedon Jun 8, 2018
(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:
mjbvz commentedon Jun 8, 2018
This issue was moved to microsoft/TypeScript#24809