Thanks for the feedback Aaron!

My 2 cents: besides whatever component is being used to handle assets, I rather cherry pick one or two scripts to be included instead of having huge “application.*” file – it’s easier to avoid clashes and conflict between styles and/or JavaScript components. On using a boolean check, I’ve done things like that but it feels cleaner to use options already baked on Rails instead of (re)building things like this on my own every now and then.

Our javascript is inside the assets directory but we want to add it only when these are galleries on the page. We are using this because our application is not a normal Rails application and in our scenario this was the best solution so far.

The Rails 4 code is doing the boolean check. We used the flushing+set path so we don’t have to copy the content_for code inside our application.

The example left me with two questions: Why isn’t your Javascript in your assets directory and included once? And wouldn’t a Boolean check be faster than repeatedly including and then flushing content?I’ll have to check out that :flush option, could be someone already thought this scenario out in Rails already.

It is fixed, thanks!

Fixed, thanks!