SchemaStore/schemastore

All properties for typescript-eslint are marked as not allowed

markedwards opened this issue · 4 comments

markedwards commented

Area with issue?

JSON Schema

✔️ Expected Behavior

When configuring a rule for typescript-eslint, all properties trigger a "not allowed" warning. See screenshot from VSCode for example.

❌ Actual Behavior

Either the properties should be added to the schema, or any property should be valid. But these warnings are worse than useless because they indicate something is wrong when it is not.

YAML or JSON file that does not work.

{
  "extends": [
    "next/core-web-vitals",
    "plugin:@typescript-eslint/strict-type-checked"
  ],
  "rules": {
    "@typescript-eslint/no-unused-vars": ["error", { "argsIgnorePattern": "^_" }]
  }
}

IDE or code editor.

Visual Studio Code

Are you making a PR for this?

No, someone else must create the PR.

hyperupcall commented

Thanks for opening an issue, I'll take a look at this tomorrow.

  • 👍1
markedwards commented

I'm happy to help if I can, but at the moment the only context I have is I see these warnings. I don't know any of the complexity leading to them.

WTPOptAxe commented

This looks like it may be causing linters to fail CI pipelines. https://megalinter.io/latest/descriptors/json_v8r/ fails with

ℹ Processing /github/workspace/.eslintrc.json
  ℹ Found schema in https://www.schemastore.org/api/json/catalog.json ...
  ℹ Validating /github/workspace/.eslintrc.json against schema from https://json.schemastore.org/eslintrc.json ...
  ✖ /github/workspace/.eslintrc.json is invalid