Skip to content

Conversation

@searls
Copy link
Contributor

@searls searls commented Sep 15, 2025

Standard validates plugin YAML like user config against a temporary, minimal default. rubocop-rails’ default.yml contains two entries that are fine when loaded by RuboCop’s plugin integrator as defaults, but trigger warnings when validated early by Standard.

This change drops those from the rules as Standard merges configs for RuboCop

  • Remove AllCops/MigratedSchemaVersion and nil AllCops/TargetRailsVersion to silence RuboCop param warnings; both deletions are behavior-neutral (epoch default skips nothing; nil TargetRailsVersion lets RuboCop infer Rails version).

  • Lint/UselessAccessModifier: Standard’s base disables this cop. Removing the rubocop-rails-specific parameters does not enable the cop and has no effect on linting outcomes.

Also adds a test that will fail the build if anything prints to stderr

Fixes #72

Standard validates plugin YAML like user config against a temporary, minimal
default. rubocop-rails’ default.yml contains two entries that are fine when
loaded by RuboCop’s plugin integrator as defaults, but trigger warnings when
validated early by Standard.

This change drops those from the rules as Standard merges configs for RuboCop

- Remove AllCops/MigratedSchemaVersion and nil AllCops/TargetRailsVersion to silence
   RuboCop param warnings; both deletions are behavior-neutral (epoch default skips
   nothing; nil TargetRailsVersion lets RuboCop infer Rails version).

- Lint/UselessAccessModifier: Standard’s base disables this cop. Removing the
  rubocop-rails-specific parameters does not enable the cop and has no effect
  on linting outcomes.

Also adds a test that will fail the build if anything prints to stderr

Fixes #72
@jasonkarns jasonkarns merged commit 4442aee into main Sep 24, 2025
10 checks passed
@jasonkarns jasonkarns deleted the rubocop-rails-warning branch September 24, 2025 13:51
@mjankowski
Copy link
Contributor

Any chance for a patch bump to get these warnings silenced ... or are we on verge of another rubocop-rails bump which will pull that along with it?

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.

Warning after upgrading to 1.39.0

6 participants