b4d539258e
Rather than take a whitelist approach to the rules, I think it would be better to start with some goal (for example, the tslint:recommended set of rules) and disable those that we don't follow. This way, it's easy to see which ones we could potentially enable. This doesn't mean that we have to follow all of them. If there are rules that we don't want, we can move them to a "Rules from tslint:recommended that we don't want" section.
47 lines
1.3 KiB
JSON
47 lines
1.3 KiB
JSON
{
|
|
"defaultSeverity": "error",
|
|
"extends": "tslint:recommended",
|
|
"rules": {
|
|
"no-null-keyword": true,
|
|
/* Rules in tslint:recommended that we don't follow yet. */
|
|
"array-type": false,
|
|
"arrow-parens": false,
|
|
"arrow-return-shorthand": false,
|
|
"ban-types": false,
|
|
"class-name": false,
|
|
"comment-format": false,
|
|
"curly": false,
|
|
"eofline": false,
|
|
"indent": false,
|
|
"interface-name": false,
|
|
"max-classes-per-file": false,
|
|
"max-line-length": false,
|
|
"member-access": false,
|
|
"member-ordering": false,
|
|
"no-angle-bracket-type-assertion": false,
|
|
"no-bitwise": false,
|
|
"no-conditional-assignment": false,
|
|
"no-consecutive-blank-lines": false,
|
|
"no-empty": false,
|
|
"no-shadowed-variable": false,
|
|
"no-trailing-whitespace": false,
|
|
"no-unnecessary-initializer": false,
|
|
"no-var-requires": false,
|
|
"object-literal-shorthand": false,
|
|
"object-literal-sort-keys": false,
|
|
"one-line": false,
|
|
"one-variable-per-declaration": false,
|
|
"only-arrow-functions": false,
|
|
"ordered-imports": false,
|
|
"prefer-for-of": false,
|
|
"quotemark": false,
|
|
"radix": false,
|
|
"semicolon": false,
|
|
"space-before-function-paren": false,
|
|
"trailing-comma": false,
|
|
"triple-equals": false,
|
|
"typedef-whitespace": false,
|
|
"variable-name": false,
|
|
"whitespace": false
|
|
}
|
|
}
|