I think there is an argument to be made for adding a convention to include 
javascript/css as precompiled elements in the asset pipeline. One of the 
main problems I have when deploying an application is that the developer 
didn't include an asset(s) to be precompiled during development. Being that 
most rails patterns are convention over configuration, adding files to 
config.assets.precompile feels odd. By moving asset precompilation from 
configuration to convention will make it feel more "integrated" in to the 
framework as a whole, and make it more natural for a Rails developer who is 
used to working with convention over configuration.

That being said, I don't think all manifests should be precompiled. There 
are many gems which contain manifests (twitter-bootstrap-rails comes to 
mind) that I would not want precompiled. We've also used manifests to wrap 
up the functionality of small backbone/angularjs apps/widgets that we want 
included in to application.js.


Nick

On Monday, April 15, 2013 3:43:20 AM UTC-4, Jarosław Rzeszótko wrote:
>
> Hi,
>
> I am a bit surprised by the need to explicitly list all the non-standard 
> manifest files in config.assets.precompile to have them precompiled by rake 
> assets:precompile. Is there any real-world scenario where one would like to 
> have a manifest file in app/assets and not have it precompiled? I don't see 
> one, so maybe it would be nicer to use a separate extension for the 
> manifests, like, say, .manifest and automatically scan the app/assets 
> directory for those files during precompilation? "Convention over 
> configuration" used to be the mantra...
>
> Cheers,
> Jarosław Rzeszótko
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to