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

Limit scanning to only relevant locations instead of whole workspace #153

Open
SharakPL opened this issue Mar 11, 2022 · 0 comments · May be fixed by #154
Open

Limit scanning to only relevant locations instead of whole workspace #153

SharakPL opened this issue Mar 11, 2022 · 0 comments · May be fixed by #154

Comments

@SharakPL
Copy link

SharakPL commented Mar 11, 2022

  • VS Code Version: 1.65.2
  • SCSS IntelliSense Version: 0.10.0
  • Operating System: Windows 10 Pro

scss.scannerExclude is good but it's hard to exclude all .scss files locations, especially in big project that use many additional plugins, modules and themes. Normally all that's required is to scan only the file(s) used by the user directly + all the imports. For example let's consider Prestashop app. It has all kinds of styles in many locations like /admin123xyz/themes, /modules, /vendor, /themes/classic etc. and this extension is scanning all of them and adds them to intellisense. This is pointless and barely helpful as it suggests many variables unavailable for my .scss file I'm working on. It should be possible to simply set this in my worskapce:

.vscode/settings.json
{
  scss.scannerRoot: "themes/my-new-theme/src/scss"
}

which would scan only this location and if scss.scanImportedFiles: true then it should also scan everything imported in this file along with all further imports based on scss.scannerDepth even outside scannerRoot location. Nothing irrelevant to this location should be scanned and suggested by intellisense.

@SharakPL SharakPL changed the title scss.scannerInclude required for better scanning Limit scanning to only relevant locations instead of whole workspace Mar 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant