Tslint 类型的推断——为什么在这里包含该类型是不好的做法？

在 VSCode 中，当我添加下面的代码时，linter tslint 会发出抱怨，它的类型是:

serverId: number = 10;

并给出以下信息:

[ tslint ]从数字字面值推断出的类型数字，删除 类型注释(不可推断的类型)

当我删除类型“数字”时，消息消失。

为什么在这里包含类型信息是不好的做法？

94273 次浏览
小开

It could be seen as noise. It's more important to type the non trivial parts

小开

It is unnecessary, it does not provide any new information. It is basically a comment saying "10 is a number".

小开
最佳答案

It is not a bad practice, but serverId: number = 10 is redundant, because number type is inferred when a property is assigned. This is what TSLint no-inferrable-types warns about:

Explicit types where they can be easily inferred by the compiler make code more verbose.

Unless there is a chance that serverId property may be initially undefined but be defined later (for instance in constructor function), number can be safely omitted.

This approach works best with noImplicitAny option because this way there are no chances that a type will be omitted by mistake because it wasn't inferred.

小开

This error is due to your configuration in tslint.json file.

Either just initialize your variable as

serverId = 10;

or 

serverId: number;

or just set your configuration for the no-inferrable-types in your tslint.json file as

no-inferrable-types: false
小开

As was mentioned above, it's technically redundant and can be considered clutter. Personally I don't care for this opinion and prefer to have both the type and the value for a variety of specific minor workflow reasons and I don't consider it to be the level of clutter warranting a rule. If you want to disable it, here's how.

  • open tslint.json
  • find the "no-inferrable-types" attribute
  • add ignore-properties to its array

relevant tslint docs https://palantir.github.io/tslint/rules/no-inferrable-types/

小开

This might be weird coming for this now, but I was getting the similar error and couldn't find the "no-inferrable-types" attribute in the tslint.json file of my angular app. I don't know why it didn't generate that in the first place but I had to insert it here

"rules": {
**"no-inferrable-types": false,**
"directive-selector": [
true,
"attribute",
"app",
"camelCase"
],

And then it worked like a charm!

P.S. This is for someone who might be wandering with the same issue as I did, or I might be wrong because no one in any of the solutions mentioned that this has to be added from our end in the json file.

小开

in tslint.json file add or complete this rule:

"no-inferrable-types": [
true,
"ignore-params",
"ignore-properties"
]
小开

If you came here looking for an ESLint solution because tslint is being deprecated, add this rule to your ESLint config:

module.exports = {
// ...
rules: {
// ...,
"@typescript-eslint/no-inferrable-types": "off",
...
},
};

提交答案