You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 14, 2021. It is now read-only.
Hello, I'm encountering some strange behavior with the bundle outdated command, and first and foremost I would like to know if this really is a bug or an expected behavior.
Having an outdated rubocop gem in my Gemfile:
gem'rubocop',groups: [:development,:test]
The command you ran
bundle outdated --group test
What you expected to happen
the gem rubocop is listed as outdated.
What actually happened
the gem rubocop was not listed as outdated.
So, here is my assumption:
When I write
gem'rubocop',groups: [:development,:test]
or
group:development,:testdogem'rubocop'end
I expect that bundler will consider that the gem is in two separate groups, as if it were declared like this:
…dale
[Outdated] Support --group with the second group for a dependency
### What was the end-user problem that led to this PR?
The problem was `bundle outdated --group NAME` wouldn't work if it was the second group for the dependency.
Closes#6115.
### What was your diagnosis of the problem?
My diagnosis was we were joining with `, ` and splitting on `,`, so subsequent groups had an additional space.
Hello, I'm encountering some strange behavior with the
bundle outdated
command, and first and foremost I would like to know if this really is a bug or an expected behavior.Having an outdated
rubocop
gem in my Gemfile:The command you ran
bundle outdated --group test
What you expected to happen
the gem
rubocop
is listed as outdated.What actually happened
the gem
rubocop
was not listed as outdated.So, here is my assumption:
When I write
or
I expect that bundler will consider that the gem is in two separate groups, as if it were declared like this:
I searched the github docs and the bundler.io docs and it did not became clear to me if my assumption is correct.
Some more examples
rubocop
gem in my Gemfile:bundle outdated
rubocop
gem in my Gemfile:bundle outdated --group development
rubocop
gem in my Gemfile:bundle outdated --group test
I also created an automated test(https://github.com/emilianoLeite/bundler/commit/e6e8d4b034390150fe26dcd3ff9cfc4b0e34da55) to confirm this behavior.
The output of said automated test is as follows:
So, again: is this a bug or an expected behavior?
If it is a bug, I would be happy to try to fix it 😄 .
Cheers.
The text was updated successfully, but these errors were encountered: