-
-
Notifications
You must be signed in to change notification settings - Fork 43
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
Feature request: define include paths #41
Comments
Would be really useful when developing with libraries like bootstrap where the pulled SCSS files are in node_modules folder. With includeFiles I could tell vscode-scss to take variables from bootstrap as well. |
Can you clarify why this is needed? And how are you compilation this without sass errors? When you import |
We need this for projects made with Angular. We define in the configuration file the folder where SASS has to resolve all the
On a component style:
|
+1 for this feature. I'm unable to get autocomplete from functions imported from |
+1
So that instead of |
I too would like to see better support for angular projects. In an angular project, you can define includePaths in |
Webstorm handles this in a really simple, effective way - you right-click (a fabulous invention - hint) and there is an option to include the folder as "assets". From then on sccs @imports consider these paths and viola you can navigate to the files |
Plus one from me too for this feature. |
I hope that vs code support this feature. |
I also need this feature for the Nrwl Nx workspace to share styles between libs |
4 years and this is still a feature request? This is so important for scss development! |
@mathiasrw, feel free to add this feature if you think it is so important for scss development |
Any update on this? I also would like to have this feature. |
This one would be great for angular projects, without it you always have to use relative paths which is really annoying in big angular applications. |
Is this still the case? VS Code has native SCSS support now, and you only need this extension for SASS, as I am aware. |
please add support for this, this is a big pain point in my process ! |
up |
Why issue has label "Need More details"? What else details are needed? |
There's no need for any more details. A contributor is rather needed, as this project seems to be dead. |
Some Sass is more useful for myself. The extension id is SomewhatStationery.some-sass . |
Yep, I switched to it. I also installed |
I would like to be able to configure include paths so that
@import
statements can reference the correct file.Consider the following configuration:
And a
.scss
-file:The following paths (relative to project root) would be considered as valid imports (and the intellisense would also recognize the first match as the actual import):
Does this seem reasonable?
PS. Discovered this extension today, loving it so far. Keep up the good work!
The text was updated successfully, but these errors were encountered: