repetition... about frontend-bootcamp HOT 5 CLOSED

It's considered good practice (at least on the team that wrote this material) to specify the types of function parameters even if they could potentially be inferred. In our main codebase, we actually have a lint rule enforcing that function parameters have types. So I think the code should stay as-is.

from frontend-bootcamp.

Looked at this more and my last comment was slightly incorrect--we actually use a TypeScript compiler option noImplicitAny so that the compiler will give an error when the type of a parameter isn't specified. That's what would give an error if we removed the type here.

What I meant by "lint" is that our team uses a tool called tslint to help enforce good coding practices in TypeScript code. If someone writes code that violates a lint rule, it will show an error when they build the code. There are similar lint tools for other languages.

from frontend-bootcamp.

Would you mind explaining what you mean in more detail?

from frontend-bootcamp.

i mean since you have this,
class TodoHeader extends React.Component<**TodoHeaderProps**, TodoHeaderState> {
, then this is okay this way,
constructor(props: `TodoHeaderProps ) {

from frontend-bootcamp.

It's considered good practice (at least on the team that wrote this material) to specify the types of function parameters even if they could potentially be inferred. In our main codebase, we actually have a lint rule enforcing that function parameters have types. So I think the code should stay as-is.

could you please tell me that lint rule?

from frontend-bootcamp.