Skip to content

Being able to use another area to view css #2

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

Open
ryanbowden opened this issue Feb 19, 2016 · 3 comments
Open

Being able to use another area to view css #2

ryanbowden opened this issue Feb 19, 2016 · 3 comments

Comments

@ryanbowden
Copy link

This
"Option to allow the user to specify directories in which the extension will look for CSS classes"

Would be very helpful for myself as where I work out CSS and JavaScript is in a different directory.

Look forward for this being implemented

@zignd
Copy link
Owner

zignd commented Feb 19, 2016

I'll begin to work on it, I just need to finish working on some other things here first.

@Jaans
Copy link

Jaans commented Feb 26, 2016

+1 for this. Alternatively, the ability to specify folders / globs that should be excluded could work too.

Our workspace has various jspm / npm packages installed and the notification at the top never completes with the errors in the status bar at the bottom relating to minified versions of installed packages (bootstrap / browser-sync / etc). Lots of these can be ignored.

@mbonaci
Copy link

mbonaci commented Oct 16, 2016

As the first step, you can just read a glob pattern from a config file placed at the root of the project (I could tolerate that, given how helpful this extension is).
In future versions you could parse webpack (gulp, ...) config and pick up file globs from there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants