Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move assets to app/assets for Rails 4 #28

Merged
merged 1 commit into from Feb 20, 2013

Conversation

stevenharman
Copy link
Contributor

In Rails 4 "loose" assets (images, fonts, etc.) in lib and vendor
are no longer precompiled by default. Rails Engines should put their
assets in their own app/assets.
See: rails/rails#7968

In Rails 4 "loose" assets (images, fonts, etc.) in `lib` and `vendor`
are no longer precompiled by default. Rails Engines should put their
assets in their own app/assets.
See: rails/rails#7968
@littlebtc
Copy link
Owner

Is there any side effects to Rails 3.x?

@stevenharman
Copy link
Contributor Author

Rails engines already look for assets in the gem's app/assets path, so this change also works for Rails 3.x.

littlebtc added a commit that referenced this pull request Feb 20, 2013
@littlebtc littlebtc merged commit de1b5b9 into littlebtc:master Feb 20, 2013
@littlebtc
Copy link
Owner

Sounds good. Merged, and I will test it again before the new gem is released.

@stevenharman
Copy link
Contributor Author

Great, and thanks! I'm actually using this gem with both a Rails 4 app (where I've verified this fix) and several Rails 3.2 apps. I can verify on one of them, if you'd like - or you can feel free to do that yourself, naturally.

Thanks again!

@littlebtc
Copy link
Owner

Version 3.0.2.2 released to RubyGems.org.
😎

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants