Jason, thank you for your honesty! I think where you and I disagree is that you call it a "use case", as though it's part of one applications particular business logic, whereas IMO it's a part of the framework that should "just work", because who wants to maintain 2 separate stylesheets--one for dynamic pages and one for static ones--or to have to write their own deployment scripts to tell some files where to find the assets, when Rails already has that feature.
At this point, I'm leaning more towards just creating a new gem to handle this, instead of submitting a PR to rails. We'll see if I get some time to do that in the next few weeks. On Monday, August 10, 2015 at 1:35:43 PM UTC-4, Jason King wrote: > > I can't speak for others, but for me it meant that I had no interest in > the idea. > > The suggestions in that PR of putting non-fingerprinted files in > `public/assets` reveals a misunderstanding of how you're meant to configure > that directory for long cache expiry (and hence, a misunderstanding of the > entire point of the asset pipeline and fingerprinting files). > > Your suggestion is at least feasible, although I think (and in my > experience) the use case you explain is much more easily resolved by adding > some ERB processing into your deploy scripts. It's basically (as far as I > can tell) your same idea, but just done in your own rake task as part of > your deploy instead of added to the existing precompile task. > -- 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 rubyonrails-core+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-core@googlegroups.com. Visit this group at http://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/d/optout.
