Skip to content

Using require: rubocop/cop/internal_affairs causes warnings #13328

@splattael

Description

@splattael

Expected behavior

The following RuboCop config emits warnings:

---
require:
  - rubocop/cop/internal_affairs

AllCops:
  NewCops: enable

InternalAffairs/CopDescription:
  Enabled: false
peter@happy ~/devel/rubocop-test$ rubocop
Warning: InternalAffairs/CopDescription does not support Enabled parameter.

Supported parameters are:

  - Include

Inspecting 0 files


0 files inspected, no offenses detected

Actual behavior

The warning should be no emitted.

Steps to reproduce the problem

  1. Create a directory
  2. Copy+paste config above
  3. Run rubocop

RuboCop version

$ [bundle exec] rubocop -V
peter@happy ~/devel/rubocop-test$ rubocop -V
1.66.1 (using Parser 3.3.5.0, rubocop-ast 1.32.3, running on ruby 3.2.4) [x86_64-linux]

I believe this error is due to missing configuration directives in config/internal_affairs.yml added by #13212.

We should probably add all possible configuration cop rules and directions similar what we do in config/default.yml.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy