-
Notifications
You must be signed in to change notification settings - Fork 16
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
Add lookup_chain customizability #162
Add lookup_chain customizability #162
Conversation
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.
👌
hey @Spone is there anything I need to do to get this PR merged? |
I just want @nicolas-brousse to have a look before we merge this! Thanks for your patience :) |
Hi @joelzwarrington looks good to me. Thank you for this PR and your patience! Could you add a line in the Changelog and rebase from |
Need this 🙏🏻 |
5c36856
to
3ec1381
Compare
hey @Spone / @nicolas-brousse do you have any idea when a new version will be released? Are there any other features you want included before that happens? I'm currently using the git source in bundler but would be nice to use versions from https://rubygems.org |
I didn't have time yesterday to do it after merging this. But I plan to do it today |
@joelzwarrington |
Component
suffix optional in lookup #80Adds configuration to determine how components are found, so one wouldn't need to use the
Component
suffix in their components.Added documentation to the README.md to configure this option