Jump to definition would ideally also work for imports (specifically named imports).
Example:
// You can import API functions like this from D3.js.
import { select } from 'd3';
// You can import local ES6 modules like this. See message.js!
import { message } from './myMessage';
// This line uses D3 to set the text of the message div.
select('#message').text(message);
I should be able to click on select on the last line, and have jump to the import.
Possible outcomes:
Ideally (stretch goal) it would open the definition of the exported variable in the other file (e.g. import { foo } from './foo'; - this would only work for local files
Initially (easier goal) - it should just jump to the import line (this is all we can do for packages e.g. d3 at the moment)
curran
commented
2 weeks ago
Jump to definition would ideally also work for imports (specifically named imports).
Example:
I should be able to click on
selecton the last line, and have jump to the import.Possible outcomes:
import { foo } from './foo';- this would only work for local filesd3at the moment)