Open bughit opened 5 years ago
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.
:before => :load_config_initializers
Any idea how to fix this? Which hook to use instead?
https://github.com/metaskills/less-rails/blob/8f9835372c3759c5c31c6799231925441baf4504/lib/less/rails/railtie.rb#L28
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.