@use and @forward do not trigger intellisense

[qzmfranklin]

• VS Code Version: 1.39

• SCSS IntelliSense Version: [email protected]

• Operating System: Ubuntu 18.04.3

Reproducible Case:

foo/_bar.scss:

$var1: 'Mono';
$var2: 'Roboto';

foo.scss:

@use 'foo/bar';

foo.   // <---------- expect intelisense to show `$var1` and `$var2` as candidates, 
         // but not showing

[JessebotX]

I believe this is a duplicate of https://github.com/mrmlnc/vscode-scss/issues/98. Looks like its not released yet

[mrmlnc]

Looks like #98 cannot resolve this issue.

[qzmfranklin]

@mrmlnc

Thanks for putting time on this issue. Appreciated.

[xzilja]

Wasn't able to trigger autocomplete neither by using @use nor @use ... as moduleName

[kawinie]

Myself included

[proclml]

@mrmlnc Does this issue still being tracked?

[dperolio]

Yes please. :(

[dsuttonpreece]

Would love to see this working :)

[BladeMF]

Yes please.

[ej52]

@mrmlnc any chance this issue will be resolved?

[clokken]

No update on this?

[laschon]

Is this extension still alive? The lack of this functionality unfortunately stops us from refactoring our mixins and start using the @use statement as intended, since it would impede the development rather than speeding it up.

[slynagh]

This one thing would make my life so much better.

[blutorange]

Just for reference, I also noticed the following behavior:

@use "../../style/theme.scss";
div {
    font-size: theme.$some-variable;
}

(where $some-variable is defined in theme.scss)

Here it does trigger intellisense and you can navigate to some-variable by clicking on it -- however, it takes you to the wrong file. When you hover over it, it also says the variable is referenced implicitly, even though the file with the variable is referenced explicitly via @use

[tunttunen]

Would be important to get this implemented...

[codethief]

Another example of what's not working:

_foo.scss

$color: #ffffff;

_main.scss

@forward "foo" as foo_*;

example.scss

@use "main.scss";

.bar {
    color: main.$foo_color;
}

The extension cannot resolve $foo_color when Ctrl+clicking on it and it also doesn't offer any suggestions when typing color: main..