Add eager_load_paths instead of autoload_paths #200
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue due uninitialized constant #198 On Rails > 5 versions.
One way to fix it is to add this to your
Rails.application.configure
environment filebut it seems the gem should use
eager_load_paths
instead ofautoload_paths
.https://www.bigbinary.com/blog/rails-5-disables-autoloading-after-booting-the-app-in-production
besides this change I notice an issue with
factories
directory when useeager_load_paths
I wonder why
solidus_dev_support
wants the factories atlib
folder if those files are for testing onlyhttps://github.com/solidusio/solidus_dev_support/blob/master/lib/solidus_dev_support/testing_support/factories.rb