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

[PLAT-1264]: Upgrade snap-style Rubocop Version to 1.22.3+ #11

Closed
wants to merge 3 commits into from

Conversation

orenmagid
Copy link
Contributor

@orenmagid orenmagid commented Jan 9, 2024

What

Closes https://snapsheettech.atlassian.net/browse/PLAT-1264 by upgrading Rubocop to 1.22.3.

snap-style isn't compatible with Ruby 3.1:

Error: RuboCop found unknown Ruby version 3.1 in `.ruby-version`.
Supported versions: 2.3, 2.4, 2.5, 2.6, 2.7, 3.0

Why

Version constraint defined on the rubocop dependency is too strict and doesn't allow more recent versions. 1.14 is compatible with Ruby 3.1, but that introduced an issue that isn't fixed until 1.22.3.

How

Relax constraint to allow the use of a newer version supporting Ruby 3.1.

@@ -169,3 +169,186 @@ Layout/EmptyLineAfterGuardClause:

Migration/DepartmentName:
Enabled: false

# The following cops were added between 0.92.0 and 1.14.0
Copy link
Contributor Author

Choose a reason for hiding this comment

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

These are all new cops that were added or enabled since Rubocop 0.92.0. I've gone ahead and disabled them until further review.

@orenmagid
Copy link
Contributor Author

I was beat to the punch: #10

Copy link

@petermarathas petermarathas left a comment

Choose a reason for hiding this comment

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

This seems okay to me to quickly add ruby version support, but I'd like to know what the backend committee thinks about ignoring all of these pending rules.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants