Skip to content
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

Support go to definition for import styles #29880

Closed
AlexandrAnash opened this issue Jun 29, 2017 · 1 comment
Closed

Support go to definition for import styles #29880

AlexandrAnash opened this issue Jun 29, 2017 · 1 comment
Assignees
Labels
feature-request Request for new features or functionality javascript JavaScript support issues upstream Issue identified as 'upstream' component related (exists outside of VS Code)

Comments

@AlexandrAnash
Copy link

  • VSCode Version: 1.13.1
  • OS Version: Windows 10 Pro

Steps to Reproduce:
When I click f12 or "go to definition", I remain in the same file
baseinput
baseinput_folder
The same thing when I click in the file itself .scss
baseinput scss-06-29 21 09 04

Will this be supported?

Perhaps such a problem is already known for this case, but i not found :(
Reproduces without extensions: Yes

@mjbvz mjbvz added feature-request Request for new features or functionality javascript JavaScript support issues labels Jun 29, 2017
@mjbvz
Copy link
Collaborator

mjbvz commented Jun 30, 2017

I've opened #29899 to track go to definition for @imports in css/sass

In js and ts, we currently don't include support for jumping to non js/ts files. The discussion for this is being tracked here: microsoft/TypeScript#15146 An existing VSCode extension may also provide this functionality, but I don't know which ones to suggest off the top of my head

Closing as upstream / split into #29899

@mjbvz mjbvz closed this as completed Jun 30, 2017
@mjbvz mjbvz added the upstream Issue identified as 'upstream' component related (exists outside of VS Code) label Jun 30, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature-request Request for new features or functionality javascript JavaScript support issues upstream Issue identified as 'upstream' component related (exists outside of VS Code)
Projects
None yet
Development

No branches or pull requests

2 participants