We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Following #121 and #136, what about calling this line:
config.paths.add "frontend/components", eager_load: true
directly from the gem instead of adding it to config/application.rb when running the install generator.
config/application.rb
Let's make a list of advantages and potential drawbacks!
The text was updated successfully, but these errors were encountered:
If you load it directly from gem, you loose advantage of changing default root path (https://github.com/komposable/komponent#change-default-root-path). But maybe not an issue to remove that option ?
Sorry, something went wrong.
Can't we use the Rails.application.config.komponent.root value in config.paths.add in case it's called from the gem?
Rails.application.config.komponent.root
config.paths.add
It's what
komponent/lib/komponent/engine.rb
Line 55 in eb4267b
No branches or pull requests
Following #121 and #136, what about calling this line:
directly from the gem instead of adding it to
config/application.rb
when running the install generator.Let's make a list of advantages and potential drawbacks!
The text was updated successfully, but these errors were encountered: