Closed josemigallas closed 4 years ago
I ran $ bundle remove capybara
on the given Gemfile with Bundler 2.1.4 which behaved as expected. Can you try this on the latest Bundler version and let us know the result?
$ bundle remove capybara
Removing gems from /Users/colby/Desktop/test/Gemfile
capybara (~> 2.18) was removed.
$ git diff
─────────────────────────────────────────────────────────────────────────────────────────────────────
modified: Gemfile
─────────────────────────────────────────────────────────────────────────────────────────────────────
@ Gemfile:199 @ group :test do
gem 'rack-no_animations', '~> 1.0.3'
gem 'simplecov', '~> 0.10.0'
- gem 'capybara', '~> 2.18', source: 'https://rubygems.org'
gem 'xpath', '~>2.1'
gem 'selenium-webdriver', '~> 3.142', require: false
Description When removing a gem from my Gemfile with
bundle remove capybara
, it results in the following diff:The output of the command being:
My findings so far: Apparently the only afffected gems are
rubocop
andsource2swagger
and only when located at the end of eachgroup
. Also if removing them, theend
keyword is not removed, for examplebundle remove rubocop
will result in:Env: Bundler version 1.17.3 ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-darwin19]