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

less-rails initializer causes load_config_initializers to run too early, before other gem initilizers #150

Open
bughit opened this issue Jan 23, 2019 · 1 comment

Comments

@bughit
Copy link

bughit commented Jan 23, 2019

see rails/rails#35025

The default expectation is that by the time app initializers run, gems are fully initialized.

According to @rafaelfranca the :before => :load_config_initializers breaks that expectation by moving load_config_initializers up.

@simi
Copy link
Collaborator

simi commented Apr 11, 2020

Any idea how to fix this? Which hook to use instead?

initializer 'less-rails.before.load_config_initializers', :before => :load_config_initializers, :group => :all do |app|

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

2 participants