Closed agenteo closed 10 years ago
Thanks for the info. Yeah, this is a known problem, but poorly understood. Something changed in how assets work in development with rails 4.1. What I think has changed is that assets from gems aren't treated the same -- I remember commenting on an issue in sprockets about the difference between development and production, and I believe they've fixed it so gem assets aren't available in all environments now. I believe if we put more or less that line in the gem it will work, but I'm unsure how to make it not effect other things.
For instance, we can't say we want to compile all .js files, because that would mess up other things. But we also don't want to maintain a list of assets that could be used from the gem -- that also sucks. So... unsure how we can solve it.
I see, I'd like to give you my input but I want to confirm I understand how it used to work first.
was: https://github.com/modeset/teaspoon/blob/master/lib/teaspoon/engine.rb:18
Teaspoon::Engine.append_asset_paths(app.config.assets)
the place in charge of loading the assets?
Hi,
Ruby 2.1.0 Rails 4.1.0
I created a:
rails new teaspoon-sandbox --skip-active-record
added
teaspoon
to the gemfilerun:
rails g teaspoon:install
and when I run
bundle exec rake teaspoon
I get the error [1]So I followed the suggestion in the error, and there were 3 files that I had to add to an initializer as follows:
after the rake task works fine.
I wonder if this is an expected step, if I overlooked something or if something is missing in the install generator.
Cheers.
[1]