Closed roryabraham closed 2 months ago
Makes sense to me.
@tommy-mitchell Any reason you went with never
? I noticed you used key T
in your issue: https://github.com/sindresorhus/type-fest/issues/652#issue-1823667703
I didn't add the never
constraint, that was introduced when RequireAllOrNone
was created in #254.
We're just inconsistent in general with our RequireX
types - some have an optional second parameter, others don't. I think all of them should, personally.
Alright. Let's do it.
Thanks all! 🚀
Minor suggestion for an enhancement - make the second argument to
RequireAllOrNone
optional:i.e:
RequireAllOrNone<MyType>
would be functionally equivalent toRequireAllOrNone<MyType, keyof MyType>
Upvote & Fund