Please enforce No Explicit Any

[martin-braun]

Suggestion

Nobody likes to see the usage of any, please consider enforcing the policy.

[RebeccaStevens]

Could you explain what you mean.
This codebase isn't using any anywhere (except here, where their use shouldn't be noticeable to end users)

[martin-braun]

@RebeccaStevens This is exactly what I meant. It's good that it's not exposed, but it's not very welcomed to see. Please see this comment to understand where I'm coming from.

Can't we get rid of those anys as well?

[RebeccaStevens]

I would remove them, if possible, but I believe I had issues getting things to work without them.

Those anys are just generics within an extends clause of a conditional type.
Those lines essentially say "is given value a key that exists in the interface DeepMergeMergeFunctionURItoKind? The generics of that interface are not important".