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

Can't ctrl+click on paths #50519

Closed
kasvtv opened this issue May 26, 2018 · 4 comments
Closed

Can't ctrl+click on paths #50519

kasvtv opened this issue May 26, 2018 · 4 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s) javascript JavaScript support issues

Comments

@kasvtv
Copy link

kasvtv commented May 26, 2018

  • VSCode Version: 1.23.1
  • OS Version: W10

Whether it's in SCSS or JS, I cannot ctrl+click on any of my imports in any of my files! I was excited about switching to this editor, but this totally breaks usability for me. Doesn't matter if I use require or import (or @import in scss's case). "Go to definition" also doesn't work as it shows:

vscode bug

Seems like it does not recognize it as a path?

Steps to Reproduce:

  1. Import any file through either JS or SCSS
  2. Place cursor inside the path string
  3. Press F12

Does this issue occur when all extensions are disabled?: Yes!!

PS: I can't see any error messages in the dev console.

@vscodebot vscodebot bot added the javascript JavaScript support issues label May 26, 2018
@mjbvz
Copy link
Collaborator

mjbvz commented May 29, 2018

Please provide a Javascript example as well. Share both the code (as text) and a description of your project structure

@mjbvz mjbvz added the info-needed Issue requires more information from poster label May 29, 2018
@aeschli
Copy link
Contributor

aeschli commented May 30, 2018

SCSS is a duplicate of #29899.

@kasvtv
Copy link
Author

kasvtv commented May 31, 2018

Allright, I have at least found the issue with JavaScript.

I was reworking the architecture of a very old project my employer still had lying around. It had lots of nastyness with many separate files building a global object. So I was calling require(filepath) to a JS file that performed window.customObject = { ... } but did not actually export anything. Not sure if this is an actual issue. It was a correct filepath, just something that wasn't exporting any module.

The problem with SCSS imports is still there. It is very easily replicable:

// entry.scss (none of these imports work when hitting F12):
@import 'imported.scss';
@import 'imported';
@import './imported.scss';
@import './imported';
body {
	background-color: $myColor;
}

// imported.scss:
$myColor: #123456;

Using the following version:

Version 1.23.1
Commit d0182c3417d225529c6d5ad24b7572815d0de9ac
Date 2018-05-10T17:11:17.614Z
Shell 1.7.12
Renderer 58.0.3029.110
Node 7.9.0
Architecture x64

Problem also exists without any extensions active.

@mjbvz
Copy link
Collaborator

mjbvz commented May 31, 2018

Ok, closing this as a duplicate of #29899 then

@mjbvz mjbvz closed this as completed May 31, 2018
@mjbvz mjbvz added *duplicate Issue identified as a duplicate of another issue(s) and removed info-needed Issue requires more information from poster labels May 31, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Jul 15, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s) javascript JavaScript support issues
Projects
None yet
Development

No branches or pull requests

3 participants