rubocop
Here are 225 public repositories matching this topic...
I really like enforcing one expectation per example. But with RSpec's exception matching, you need two expect calls if you want to assert something about an exception:
expect { my_code }.to raise_error(MyErrorType) do |error|
expect(error.message).to match /something went wrong/
end
There's no way to match against the error message without first wrapping the call, and RSpec o
-
Updated
Oct 21, 2020 - Ruby
-
Updated
Oct 20, 2020 - Ruby
-
Updated
Mar 14, 2018 - Vim script
-
Updated
Oct 20, 2020 - Ruby
-
Updated
Jan 6, 2020 - Python
-
Updated
Oct 21, 2020 - Ruby
-
Updated
Aug 24, 2020 - Ruby
-
Updated
Sep 12, 2020 - Ruby
-
Updated
Jun 12, 2020 - Ruby
-
Updated
Oct 19, 2020 - Ruby
Add more tests
-
Updated
Oct 9, 2020 - Ruby
-
Updated
Oct 9, 2020 - Ruby
-
Updated
Oct 5, 2020 - Ruby
-
Updated
Feb 12, 2019 - Ruby
Improve this page
Add a description, image, and links to the rubocop topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the rubocop topic, visit your repo's landing page and select "manage topics."
Is your feature request related to a problem? Please describe.
Gemspec/RequiredRubyVersion enforces that gemspec.required_ruby_version is set and then complains that it differs from TargetRubyVersion in .rubocop.yml even if it is not specified in .rubocop.yml.
Having to specify TargetRubyVersion in .rubocop.yml in addition to gemspec.required_ruby_version duplicates the information.