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

fix: Disabling the cop that enforces variable name for Exceptions #129

Merged
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,11 @@ This gem is moving onto its own [Semantic Versioning](https://semver.org/) schem

Prior to v1.0.0 this gem was versioned based on the `MAJOR`.`MINOR` version of RuboCop. The first release of the ezcater_rubocop gem was `v0.49.0`.

## 6.1.2
Copy link
Contributor

Choose a reason for hiding this comment

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

I would think this is a minor version release and not a patch.


- Disable `Naming/RescuedExceptionsVariableName` so exception variable names are less restrictive.


## 6.1.1

- Lock `rubocop-rspec` below `v2.28.0` to avoid an upstream namespacing issue.
Expand Down
3 changes: 3 additions & 0 deletions conf/rubocop.yml
Original file line number Diff line number Diff line change
Expand Up @@ -50,6 +50,9 @@ Naming/MethodParameterName:
- ex
- id

Naming/RescuedExceptionsVariableName:
Enabled: false

Naming/VariableNumber:
Enabled: false

Expand Down
2 changes: 1 addition & 1 deletion lib/ezcater_rubocop/version.rb
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
# frozen_string_literal: true

module EzcaterRubocop
VERSION = "6.1.1"
VERSION = "6.1.2"
end
Loading