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

Change configuration setup to allow gem to be left out of default group #10

Open
pjmorse opened this issue Mar 21, 2023 · 0 comments
Open

Comments

@pjmorse
Copy link
Contributor

pjmorse commented Mar 21, 2023

Currently the suggested setup for GemFresh, as in the README, is to have an initializer (at config/initializers/gem_fresh.rb). Running the initializer requires the constant GemFresh be defined in the application, which is fine as long as the gem is in the default group.

However, if a developer wants to leave the gem out of the deployed application by putting the gem in the development or test groups (e.g. by putting it in those groups in the Gemfile), then the initializer will raise NameError: uninitialized constant GemFresh whenever the application starts up.

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

No branches or pull requests

1 participant