feat: added the require-mock-type-parameters rule

[marekdedic]

So far the rule is only implemented for vi.fn(). I'd also like to implement it for other functions, specifically these are the ones which have a generic type argument that is not present in the function parameters and so won't be automatically inferred:

• vi.importActual
• vi.importMock

but these two I think should be behind a configuration flag, because I can imagine people not wanting to bother with them. What do you think? Anyway, I wanted to get some feedback (@veritem) on the design before proceeding.

I think this rule should also be turned off for files that aren't TypeScript, so you have any infrastructure set up for this?

Thanks for your feedback.

Closes #649

[veritem]

but these two I think should be behind a configuration flag, because I can imagine people not wanting to bother with them. What do you think? Anyway, I wanted to get some feedback (@veritem) on the design before proceeding.

@marekdedic I agree, let's make them optional unless the user explicitly enables them using configuration files.

I think this rule should also be turned off for files that aren't TypeScript, so do you have any infrastructure set up for this?

I don't have specific ways to turn off rules for typescript files. But there is a configuration setting to enable typescript's type checker -- refer to this section on how we handle it

eslint-plugin-vitest/src/rules/expect-expect.ts

Line 46 in e2365c4

const settings = parsePluginSettings(context.settings)

[marekdedic]

Hi,
great, I added support for importActual and importMock behind a configuration option. The thing you linked is for type checking, which is not the case here - the rule works perfectly fine without typechecking, it just doesn't make sense without typescript at all. But if you don't really check that elsewhere, we can just leave it as is and leave it to users to turn this rule off where they want to...