New rules suggestion to prevent common coding typos (length and constructor)

As a non native english developper I lost a huge amount of time fixing the same typos again and again.

I fixed common constructor typos using id-blacklist rule. It’s safe because who would ever use those IDs:

{
  "id-blacklist" : ["error",
    "contructor",
    "contrutor",
    "construtor",
    "construcor",
    "constuctor"
  ]
}

I also fixed length typos using no-restricted-properties, It’s safe because what evil mind would ever use lenght in any code?!

{
  "no-restricted-properties" : ["error", {
    property : "lenght"
  }]
}

Could we have this directly within eslint-config-airbnb-base?

This could save the world a huge amount of time 😉

Related issue: https://github.com/eslint/eslint/issues/8940

PS: I’m pretty sure there is many other use cases, for example this related issue about propTypes typos: https://github.com/yannickcr/eslint-plugin-react/issues/65 (and see also react/no-typos)

[ljharb]

Non-English speakers are important too!

I do think that it’s not something we should add; but I’d love to see a core no-typos rule.

[yvele]

Instructive discussion… it’s maybe more a problem for non native english developers (I’m french).

We also use a lot of classes on non react projects.

We will keep those rules added to our own rules (inherited from airbnb).

I agree eslint-config-airbnb-base should be kept as simple as possible (for maintenance, etc.)

Feel free to close the issue, and thanks again for your time 😉