no-any-as-parameter

[jpike88]

It would be good as a gradual tightening of types, to have a rule that bans the passing as an item with type any or any[] as a parameter to another function, even if the function has a parameter with type any in its definition.

This allows for the flexibility of having such functions remain, but ensures that stuff going in was coerced to an explicit type beforehand.

[unvalley]

Hi, isn't noExplictAny enough? I would appreciate it if you could give me an example.

[aselcuktuncer]

hey, it's been a while, but I'd like to leave a comment. i have a function like this:

const getErrorMessage = () => {
    try {
      const parsedErrorMessage = JSON.parse(errorMessage ?? '');
      if (Array.isArray(parsedErrorMessage)) {
        return parsedErrorMessage[0]?.message; // here the return type is 'any'
      }
      return errorMessage ?? '';
    } catch (e) {
      console.error(e);
      return errorMessage ?? '';
    }
  };

and later i used this function here and it did not throw any linting error. but here I was expecting an error like no-any-as-parameter and to be forced to specify typeof 'parsedErrorMessage[0]?.message'
// message?: string | undefined
<ErrorDisplay message={getErrorMessage()} />

btw i am using the recommended lint rules.

[jpike88]

errorMessage ?? ''

That makes me sad. No comment otherwise