-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
Option to ignore css Files #24
Comments
Hey, @DG606 . Do you have a minimal example that I can use to reproduce that behavior? Also, can you compile the files normally using the Dart Sass executable? If yes, then can you share the command and the file that is being compiled? |
Hi, The maven plugin includes all css Files for compiling. So i get an error. As an workaround I rename my *.css File to *.Css . So the plugin ignores it ;-) but this feels like a bad solution. cssfile content (the '#{resource' will be replaces later at deployment of jsf application which i can't change: |
Hey, @DG606. Thanks for sharing a sample CSS file. I see that that's the same behavior that you get if you use Dart Sass CLI in the many-to-one mode and the input folder and the output folder are different. So the plugin is behaving the same way the CLI does. Try to compile files in folder A to a different folder B and you'll get the same error. As a workaround, can you try setting the |
Hi, |
You're leveraging that feature of the CLI: if there's a .css file inside a directory and the destination is the same folder, then it won't be compiled, so that's why you see no error. You have to assume that .css files will be compiled if the source and destinations are different. That being said, this is not something we'll fix so that we don't override the CLI behavior. Just set |
Hi,
i have problems that sass won't compile my css Files (Error: Interpolation isn't allowed in plain CSS) but it is not needed to compile css!
Is it possible to add an extra option to ignore css Files? Or maybe support of * in inputFolder like src/main/webapp/resources/**/*.scss?
Thanks
Daniel
The text was updated successfully, but these errors were encountered: