Make check-types configurable

[golopot]

Users should be able to set the preference of types. The option could looks like this:

{
  '@typescript-eslint/ban-types': [
    'error',
    {
      types: {
        // ban type `Foo` using the default error message
        Foo: null,

        // ban type `Bar` with a custom message.
        Bar: "Don't use Bar!",

        // ban type `String` and tell the plugin how to fix it.
        String: {
          message: 'Use string instead',
          fixWith: 'string',
        },
      },
    },
  ],
};

See @typescript-eslint/ban-types.

As a side note, ban-types is a better name than check-types. The name check-types could mean "check type is valid", "check type is consistent to how it is used" or "check the style of types".

[brettz9]

See my comment on a related issue, i.e., per issue #107 I think we might look at something like this if reimplementing valid-jsdoc's preferType.

[brettz9]

Closed by #247. Thanks for the great idea! I tweaked it a little in the implementation, but it is similar as you can see in the docs. (also connects to options with check-types and no-undefined-types)

[gajus]

🎉 This issue has been resolved in version 6.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀