feat(ct): react optional declaration merging hooks config

[sand4rt]

• Partial fix for: [Feature] improve type safety hooksConfig #19933
• @pavelfeldman this is a split from: feat(ct): resolve hooksConfig import refs #30455 (comment)
• Will follow up with the other frameworks if this one gets through

[dgozman]

We prefer to not override types globally in Playwright. Can we help the user in some other way? Perhaps by casting test exported from the package like const test = baseTest as SomeTestDeclaration<SpecificHooksConfig>? Or by extending with a mnt fixture that is mount<SpecificHooksConfig>?

[sand4rt]

We prefer to not override types globally in Playwright.

Normally i wouldn't use declare module in this way, but i think this is a good use case. Especially because the mount() is called so many times. The beforeMount<T>, afterMount<T>() and mount<T>() can also still be specified manually for the people who think it's too much magic.

Can we help the user in some other way?

I don't think there's another way to make the hooksConfig in beforeMount(), afterMount() and mount() automatically type-safe with a single type definition right? type-casting const test would solve a part of the problem.

[dgozman]

I don't think there's another way to make the hooksConfig in beforeMount(), afterMount() and mount() automatically type-safe with a single type definition right? type-casting const test would solve a part of the problem.

That's right. However, you only write beforeMount() and afterMount() once, so explicitly typing them is not a big deal. It looks like the main goal is to avoid mount<T> every time.

[github-actions]

Test results for "tests 1"

15 passed
✔️✔️✔️

Merge workflow run.