ReturnCount JSON Schema is outdated

[TWiStErRob]

Expected Behavior

https://json.schemastore.org/detekt.json

        "ReturnCount": {
          "type": "object",
          "properties": {
            "active": {
              "type": "boolean"
            },
            "excludedFunctions": {
              "type": "some kind of array"
            },
            ...
          }
        },

Observed Behavior

        "ReturnCount": {
          "type": "object",
          "properties": {
            "active": {
              "type": "boolean"
            },
            "excludedFunctions": {
              "type": "string"
            },
            ...
          }
        },

Steps to Reproduce

Edit detekt.yml in IDEA and add

  ReturnCount:
    max: 3
    excludedFunctions:
      # Ignore MenuProvider.onMenuItemSelected, Activity.onOptionsItemSelected,
      # and Fragment.onOptionsItemSelected, because they have a special structure for bug prevention.
      - 'onMenuItemSelected'
      - 'onOptionsItemSelected'

if you follow the schema you get:

Property 'style>ReturnCount>excludedFunctions' should be a YAML array instead of a comma-separated String.

if you follow the warning you get:

Schema validation: Incompatible types. Required: string. Actual: array.

There's no winning :)

Context

My doc update in #5062 triggered #5063 which was fixed by #5081, but that made the schema on schemastore outdated. Would be solved by #4162

Your Environment

• Version of detekt used: 1.22.0

[3flex]

In the meantime, someone can update the schema on schemastore. This isn't technically a detekt bug.

[TWiStErRob]

Raised SchemaStore/schemastore#2623

[TWiStErRob]

@3flex I guess we agree that it'll be a Detekt bug, once #4162 is done, and we own the schema. 😅

[3flex]

Looks like it was merged, thanks for opening the PR! Yes, if detekt project starts generating or hosting our own schema, this would definitely be a bug.