prompts don't work correctly when using @use with namespace
See original GitHub issue- VS Code Version: 1.44
- SCSS IntelliSense Version: Version: 0.9.0
- Operating System: Windows 10
Reproducible Case:
the extension’s prompts working correctly with @use
only when importing with asterisk like @use 'firstfile' as *
Steps to Reproduce:
- create 2 scss files
- in first file write some mixin
- in second file import first file with namespace as
@use 'first'
or like@use 'first' as mixins
; - try to use your mixin as
@include first.
or@include mixins.
then you won’t see some suggest. And it will never suggest you the namespace (first
ormixin
, that we used before)
Issue Analytics
- State:
- Created 3 years ago
- Reactions:24
- Comments:5
Top Results From Across the Web
Is using namespace..like bad? [duplicate] - Stack Overflow
There is no problem using using namespace std in your source file when you make heavy use of the stl and know for...
Read more >FAQ: things you need to know about namespaces - PHP
First, the current namespace name is prepended to name . Finally, if the constant or function name does not exist in the current...
Read more >Visual studio 2022 - Disable auto sync namespace and folder ...
I work with MAUI and i get some problems with my xaml pages if visual studio change the namespaces if i drag some...
Read more >Auto import | PhpStorm Documentation - JetBrains
Import the namespace manually using a quick-fix. The use statement is added to the imports section, but the caret does not move from...
Read more >In-App Guidance Prompts FAQ - Salesforce Help
Prompts don't require any additional licenses to show to end users. As an admin or designated user, ... Use the buttons to guide...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I agree on @AradAral request.
@import
is deprecated already and using namespaces is the default behaviour.Imho, Intellisense should look for imported modules in the current sass file only and using the new dart-sass syntax. This should improve speed and would be much more efficient since it would only suggest vars that you actually needs.
This should definitely be implemented. It has now been about 2/3 years that the new module system (i.e.
@use
/@forward
) has been added to Sass, but we still don’t have proper intellisense for it 😦 @mrmlnc Any ideas, Denis?