forked from palantir/tslint
-
Notifications
You must be signed in to change notification settings - Fork 0
/
noObjectLiteralTypeAssertionRule.ts
100 lines (89 loc) · 3.75 KB
/
noObjectLiteralTypeAssertionRule.ts
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
/**
* @license
* Copyright 2017 Palantir Technologies, Inc.
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
import {
isAssertionExpression,
isObjectLiteralExpression,
isParenthesizedExpression,
} from "tsutils";
import * as ts from "typescript";
import * as Lint from "../index";
import { codeExamples } from "./code-examples/noObjectLiteralTypeAssertion.examples";
const OPTION_ALLOW_ARGUMENTS = "allow-arguments";
interface Options {
allowArguments: boolean;
}
export class Rule extends Lint.Rules.AbstractRule {
/* tslint:disable:object-literal-sort-keys */
public static metadata: Lint.IRuleMetadata = {
ruleName: "no-object-literal-type-assertion",
description: Lint.Utils.dedent`
Forbids an object literal to appear in a type assertion expression.
Casting to \`any\` or to \`unknown\` is still allowed.`,
rationale: Lint.Utils.dedent`
Always prefer \`const x: T = { ... };\` to \`const x = { ... } as T;\`.
The type assertion in the latter case is either unnecessary or hides an error.
The compiler will warn for excess properties with this syntax, but not missing required fields.
For example: \`const x: { foo: number } = {}\` will fail to compile, but
\`const x = {} as { foo: number }\` will succeed.`,
optionsDescription: Lint.Utils.dedent`
One argument may be optionally provided:
* \`${OPTION_ALLOW_ARGUMENTS}\` allows type assertions to be used on object literals inside call expressions.`,
options: {
type: "array",
items: {
type: "string",
enum: [OPTION_ALLOW_ARGUMENTS],
},
},
optionExamples: [true, [true, OPTION_ALLOW_ARGUMENTS]],
type: "functionality",
typescriptOnly: true,
codeExamples,
};
/* tslint:enable:object-literal-sort-keys */
public static FAILURE_STRING =
"Type assertion on object literals is forbidden, use a type annotation instead.";
public apply(sourceFile: ts.SourceFile): Lint.RuleFailure[] {
return this.applyWithFunction(sourceFile, walk, {
allowArguments: this.ruleArguments.indexOf(OPTION_ALLOW_ARGUMENTS) !== -1,
});
}
}
function walk(ctx: Lint.WalkContext<Options>): void {
return ts.forEachChild(ctx.sourceFile, function cb(node: ts.Node): void {
if (
isAssertionExpression(node) &&
node.type.kind !== ts.SyntaxKind.AnyKeyword &&
// Compare with UnknownKeyword if using TS 3.0 or above
(!!(ts.SyntaxKind as any).UnknownKeyword
? node.type.kind !== (ts.SyntaxKind as any).UnknownKeyword
: node.type.getText(ctx.sourceFile) !== "unknown") &&
isObjectLiteralExpression(
isParenthesizedExpression(node.expression)
? node.expression.expression
: node.expression,
) &&
!(ctx.options.allowArguments && isArgument(node))
) {
ctx.addFailureAtNode(node, Rule.FAILURE_STRING);
}
return ts.forEachChild(node, cb);
});
}
function isArgument(node: ts.Node): boolean {
return ts.isCallLikeExpression(node.parent);
}