-
Notifications
You must be signed in to change notification settings - Fork 17
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
Allow execution within the Asset Pipeline #19
Comments
I'm not sure that the conversion to a pipeline plugin is necessary. I think sbt-filter will only perform its filtering when a production build is triggered. I'll try to find some time to look at this this evening. |
@irundaia , the purpose would be to have something similar to sprockets. To process the Resources as a whole and be able to output 1 or more minified javascript and stylesheets file. |
@driverpt, I fail to see how this is impossible with the current approach. If sbt-filter removes the Also from the sbt-web README.md:
So if I understand this correctly, first source tasks are run. The output thereof, can then be used as desired in the filtering pipeline I might be understanding this incorrectly... Could you perhaps give a an example of how you'd want your input files to flow through your pipeline? |
I want for example When i developed an app in Grails, i used this, which has a similar sprockets behaviour. e.g.:
And the output to be
Any ideas how to achieve this ? |
e.g.:
pipelineStages := Seq(sassify, filter, digest, gzip)
So that
filter
can filter out .scss files from the result.The text was updated successfully, but these errors were encountered: