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
Deprecate bundle plugin install --local-git=
#7048
Deprecate bundle plugin install --local-git=
#7048
Conversation
6e065d4
to
63407e0
Compare
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.
Looks great, just added a comment to add an explicit runtime deprecation.
I think this option is mostly discoverable through CLI help, and you already included a note about deprecation there, but we print a runtime message for other deprecated flags, so I think it does not hurt to also do it here.
@ccutrer Sorry for my slow reviews, the plugin work you were doing is awesome. Whenever you're ready to continue, I am too! |
👍 I was on vacation for a week, then got Covid, so I'm a bit backlogged, but I promise to get back to it as soon as I can. |
Hope you enjoyed your vacation, and are feeling better now after Covid. Thanks so much for the work! |
51e6e5d
to
190e962
Compare
Since the flag is deprecated in Bundler 2 and will make commands using it fail in Bundler 3, this is making some specs fail. If they are unrelated to the setting itself, they can be changed to use |
190e962
to
bf118b6
Compare
The failing specs are all ones I left in to ensure the deprecated behavior still works. I've add spec filters to them so they won't run at all under bundler 3. |
Sorry for the lack of feedback here. By adding the filters, we'll lose the specs on Bundler 3, right? I think it's better to migrate the specs to use |
Ahhh, yes, I could move the specs for deprecated features there. I didn't know it existed. The specs that have the filters are already duplicates of ones that use |
Are we testing that |
bf118b6
to
e2f97df
Compare
149b929
to
f605422
Compare
I addressed what I think was left to do here. |
It's the exact same implementation as --git
f605422
to
18eb241
Compare
…-path Deprecate `bundle plugin install --local-git=` (cherry picked from commit 5c7246d)
What was the end-user or developer problem that led to this PR?
Adding the --path param, I noticed --git and --local-git have identical implementations.
What is your fix for the problem, implemented in this PR?
Keep --local-git as an undocumented alias for --git. Use the same actual implementation now. No functionality change.
Make sure the following tasks are checked