You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a change is made in say variables.sass that is referenced by say main.sass, only the variables file compiles.
Problem is the main.sass references a variable in that changed file but is not compiled so the change does not propagate.
I attempted to use --force, but this requires --update, and in this configuration it is not easy to specify the params for --update without modifying the sbt-sass codebase.
So please either:
Allow the use of --force functionality
Detect dependent files to be compiled
This would also solve:
Partials with only variables not compiled #16 #16
The text was updated successfully, but these errors were encountered:
Looking into SbtSass.scala I see that this problem originates from using modifiedSources.
This of course cannot find dependencies of variables.sass that may need to be compiled.
Why don't we change this to use the sass --watch flag which will take care of the dependency check automatically and requires no code duplication on our side?
I had some issues with getting corporate IT to install ruby/sass. So I rewrote the sbt-sass plugin to use libsass rather than sass. While doing this, I also solved the above mentioned bug. Feel free to use that plugin.
When a change is made in say variables.sass that is referenced by say main.sass, only the variables file compiles.
Problem is the main.sass references a variable in that changed file but is not compiled so the change does not propagate.
I attempted to use --force, but this requires --update, and in this configuration it is not easy to specify the params for --update without modifying the sbt-sass codebase.
So please either:
This would also solve:
Partials with only variables not compiled #16
#16
The text was updated successfully, but these errors were encountered: