Skip to content
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

Relax maximum capybara version constraint #2281

Merged
merged 1 commit into from Mar 4, 2020
Merged

Relax maximum capybara version constraint #2281

merged 1 commit into from Mar 4, 2020

Conversation

pirj
Copy link
Member

@pirj pirj commented Mar 4, 2020

fixes #1095

@pirj pirj self-assigned this Mar 4, 2020
@@ -48,7 +48,7 @@ gem 'rake', '~> 12'

gem 'mime-types', "~> 3"

gem 'capybara', '~> 2.13', require: false
gem 'capybara', '>= 2.13', '< 4.0', require: false
Copy link
Member Author

@pirj pirj Mar 4, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Checked locally, rake is green with the latest Capybara 3.x.

Changes:

  1. Capybara 3 changes the default server to Puma (doc)
    This is pretty much up to the users, rspec-rails don't depend on either.

  2. Finders (doc)
    Up to the users as well, we don't wrap first/all.

  3. Node (doc)
    We don't wrap those methods, so it's up to the users.

Update of Capybara to 3.x will only happen when Rails hits 6.1 (or when Rails will decide to bump Capybara to 3.x), and Rails' 6.0 -> 6.1 update docs should pretty much cover it.

@@ -366,7 +366,7 @@ you can run the specs and Cucumber features, or submit a pull request.
### Recommended third-party extensions

* [FactoryBot](https://github.com/thoughtbot/factory_bot)
* [Capybara](https://github.com/jnicklas/capybara)
* [Capybara](https://github.com/teamcapybara/capybara)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@@ -48,7 +48,7 @@ gem 'rake', '~> 12'

gem 'mime-types', "~> 3"

gem 'capybara', '~> 2.13', require: false
gem 'capybara', '>= 2.13', '< 4.0', require: false
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd still prefer '~> 2.13', '~> 3.0' its semantically the same but a bit clearer in my opinion. Unless its not valid for some reason?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bundler seems to combine the options passed with "and", so this fails with:

Could not find gem 'capybara (~> 2.13, ~> 3.0)' in any of the gem sources listed in your Gemfile.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fair enough!

@pirj pirj merged commit a9f9093 into master Mar 4, 2020
@pirj pirj deleted the bump-capybara branch March 4, 2020 21:00
JonRowe pushed a commit that referenced this pull request Mar 13, 2020
Relax maximum capybara version constraint
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Hard bump the capybara version
2 participants