-
Notifications
You must be signed in to change notification settings - Fork 128
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
Ensure Railtie has eager_load_paths #140
Conversation
It is possible that gems may define a Railtie without defining `eager_load_paths` (such as `dotenv-rails`), which causes this function to fail. Extend the `next` clause to ensure the existence of `eager_load_paths` to prevent this failure.
This should resolve #139 |
+1 |
Has this been fixed? I am running into the same issue. |
What's this waiting on? |
@jarednorman I imagine the CI failures, which are unrelated and I also fixed in #141 |
Maybe we should submit a PR to dotenv implementing eager_load_paths as a NOP |
Ensure Railtie has eager_load_paths
thanks a lot for the patches @alexblackie !!! |
Hi, does the fix have beed released? |
I dont think so Edwin you will need to point to github to get it On Wed, Jun 3, 2015 at 12:27 PM, Edwin Lunando notifications@github.com
Washington L Braga Jr Developer |
What are we waiting for to get this released? |
I think we need @BDQ for that |
It is possible that gems may define a Railtie without defining
eager_load_paths
(such asdotenv-rails
), which causes this functionto fail. Extend the
next
clause to ensure the existence ofeager_load_paths
to prevent this failure.