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

Update rubocop to 1.71, rubocop-rspec to 3.4 #325

Open
wants to merge 9 commits into
base: main
Choose a base branch
from
Open

Conversation

lfittl
Copy link
Member

@lfittl lfittl commented Feb 5, 2025

Plus do (some of) the stylistic fixes that newer Rubocop releases ask for, see individual commits.

This is more idiomatic, per the RSpec/ImplicitSubject rule.
… test

This has been pending for a long time, and resolving this seems out of
scope for what pg_query does when it runs its fingerprinting. We don't
gain much by keeping this, and it clutters the test output.
Its not clear what the open item here is, and this is most likely
a accidental leftover from when this code was modified in e4eff25.
All Struct objects have "length" defined (which is the number of fields
in the Struct), and it seems sensible to not override this unnecessarily.
This is in anticipation of a follow-up commit that updates the Rubocop
version to the latest and introduces new stylistic checks that seem
acceptable to enable.
This is considered more idiomatic, and gets flagged by newer Rubocop
versions.
This also lets us drop the Ruby 3.0 requirement for rubocop on CI, since
we can now use rubocop on all released Ruby versions.

Further, turn off some of the newly introduced cops that seem to add
unnecessary noise, and opt in to new cops by default (this avoids a
warning, and seems fine since we lock the rubocop version).

Also, drop inline disabling of the "Lint/EmptyWhen" lint, which is no
longer needed.
@lfittl lfittl requested a review from a team February 5, 2025 07:55
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.

1 participant