Wrong warnings in tslint.json for accepted configuration values about schemastore

[proProbe]

It seems like this is still a problem? Any ideas on this?

[omgaunicorn]

I ran into the same issue, specifically with the curly rule at first and mistakenly tried to fix it on the tslint side, but the tslint.json used here has several old schemata for rules that have changed. I'll look into making a PR with updates to those rules.

[cyrilletuzi]

Be sure to not only add the missing new rules, but also the new options and severity configuration for each rule.

For example :

"class-name": true

can now be set like this, to manage severity level :

"class-name": {
  "options": true,
  "severity": "error"
}

I hope there is something to manage this case in json schemas, or it will be a very ugly schema with a lot of duplicate code...

[timbru31]

The ban rule is also invalid since it's no longer an array of banned functions/methods since v5.4.0.
See palantir/tslint#2547

[tkrotoff]

Other TSLint rules having the same issue (Incorrect type. Expected "array"):

"interface-name": false
"trailing-comma": false
"comment-format": false
"max-classes-per-file": false
"no-console": false
"member-ordering": false

[tkrotoff]

@Martin-Wegner this can be closed now, see #339

[Martin-Luft]

@tkrotoff thank you! But unfortunately there are a lot of new TSLint rules which produces a lot of warnings. For example:

"member-ordering": [true, "fields-first"] -> Incorrect type. Expected "object"

"no-magic-numbers": true -> Incorrect type. Expected "array"

"no-void-expression": [true, "ignore-arrow-function-shorthand"] -> Incorrect type. Expected "boolean"

"ordered-imports": [true, { "import-sources-order": "case-insensitive", "named-imports-order": "case-insensitive" }] -> Incorrect type. Expected "boolean"

[tkrotoff]

@Martin-Wegner Well you can send a PR like I did