Add Precompiles

[sidnair]

I think this is the only change required for precompilation to work.

Edit: I just saw issue 9. I'll leave this issue open in case you decide against using an initializer. Sorry for the duplication.

[Maher4Ever]

Wouldn't it be better to keep the comment in the file for future reference and add the config line after it?

[sidnair]

The line above this has a comment explaining what it does: "Precompile additional assets (application.js, application.css, and all non-JS/CSS are already added)." And, since the example I removed is so similar to the new line, I don't think there's much value leaving it in. I assumed it was standard to remove the example in cases like this, but I can leave it in if it's not.

[Maher4Ever]

I understand why you choose to replace the comment, but now after looking closely to this way of adding precompiles I see 2 problems with it:

1. What if another generator wants to add an asset too to the precompiles? It might use the same kind of code and expect the comment to exist.
2. What if the user has deleted this comment and added a custem asset to the precomiles?

I'm not so familiar with rails generators so I can't suggest a better way yet, but I hope you'll see why I think this implementation is a bit dangerous.

[sidnair]

Yeah, that's a good point. I think the correct way to do might be something like:

application(nil, :env => "production") do "#{application_name}::Application.config.assets.precompile += %w( polyfills.js )" end

(from http://guides.rubyonrails.org/generators.html#application), but I'm not sure.

[sporkd]

Thanks for the work on this. I was toying with the idea of just adding the configuration inside the gem, similar to this: https://github.com/indirect/haml-rails/blob/master/lib/haml-rails.rb#L7-11

However, I don't want to force the use of polyfills.js just by virtue of loading the gem. I think perhaps the best compromize is to generate a new initializer in config/initializers. That way it can be deleted. I also don't think you want to force env production since you have full control of what environment you run the precompile rake task. So presumably it only gets run on deploy to production (or staging) anyway. But I like to run it in development sometimes just to see if it's working.

[sporkd]

For some reason I thought config.assets.precompile was in application.rb, but its in production. So using @sidnair09s example might be a good option. Sorry. I'll try and get this implemented or merged in the next day or so.