Skip to content

Sprockets cache expiration based on react-rails settings #257

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

Merged
merged 1 commit into from
May 14, 2015

Conversation

byroot
Copy link
Contributor

@byroot byroot commented May 4, 2015

Followup to #254

See #254 (comment)

cc rmosolgo

@byroot
Copy link
Contributor Author

byroot commented May 5, 2015

I rebased on top of master now that #254 is merged. But it seems tests are failing. I'll find some time to fix them.

@rmosolgo
Copy link
Member

rmosolgo commented May 5, 2015

Is version relatively new? It's throwing a NoMethodError so maybe it's not defined in some of the older Rails versions we support (3.2+)

@byroot
Copy link
Contributor Author

byroot commented May 5, 2015

No the problem is that app.assets is nil. Probably because the code I added is too soon in the initialization chain.

@byroot byroot force-pushed the cache-expiration branch from 1ad83b4 to 1dbddaf Compare May 5, 2015 17:46
@byroot
Copy link
Contributor Author

byroot commented May 5, 2015

I just moved that code on after_initialize. It should go green now. I just keep forgetting to use appraisal to test my changes.

@rmosolgo
Copy link
Member

👍 thanks again for upstreaming!

rmosolgo pushed a commit that referenced this pull request May 14, 2015
Sprockets cache expiration based on react-rails settings
@rmosolgo rmosolgo merged commit 491715c into reactjs:master May 14, 2015
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.

3 participants