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

config.assets.precompile behavior has changed #64

Closed
route opened this issue Jun 5, 2013 · 2 comments
Closed

config.assets.precompile behavior has changed #64

route opened this issue Jun 5, 2013 · 2 comments

Comments

@route
Copy link

route commented Jun 5, 2013

In earlier versions (~> 3.2) it had a proc that covered all non-js/css files as we see here
https://github.com/rails/rails/blob/3-2-stable/railties/lib/rails/application/configuration.rb#L48
Those types of files could be in the third party libraries, but for now it limits us within app/assets directory regarding this lambda https://github.com/rails/sprockets-rails/blob/master/lib/sprockets/railtie.rb#L39

Was it done intentionally? Should the third party libraries append their own settings to config.assets.precompile or we should configure it in apps? Thanks in advance!

@guilleiguaran
Copy link
Member

Yes, is intentional and third party libraries should append their own settings. See rails/rails#7968.

@route
Copy link
Author

route commented Jun 5, 2013

Thank you, missed that

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

No branches or pull requests

2 participants