-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Refactor singleton usage and make it possible to use with engines #1836
Refactor singleton usage and make it possible to use with engines #1836
Conversation
lib/webpacker/helper.rb
Outdated
# Returns current Webpacker instance. | ||
# Could be overriden to use multiple Webpacker | ||
# configurations within the same app (e.g. with engines) | ||
def current_webpacker |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps, let's call it current_webpacker_instance
just to be clear, current_webpacker
doesn't make sense. What do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
Any plans on merging this? |
Thanks @palkan 🙏 sorry it took me a while to merge |
Replaces #1808.
Added docs on how to use Webpacker from Rails engine.