feat: Add isPartialRecord guard

[kkirsche]

This begins to address #4 but is no longer a full solution.

[lazarljubenovic]

This doesn't work correctly. The simplest example is for an empty object: you'll always return true, because the array of key/value pairs you're checking is empty. In TypeScript, Record is exhaustive: the object of type Record<'a' | 'b' | 'c', number> required all three keys to exist, but you function will return true as long as each existing satisfies the predicate. For example, {} will pass, but it should not.

Unfortunately, I don't think there's an easy to fix it properly. The only thing we can do is assert that an object is of type Partial<Record<K, V>>, but this should be properly documented and reflected in the function name to avoid confusion.

[kkirsche]

I'm happy to either close this due to this limitation or update it to be isPartialRecord, do you have a preference which direction is gone?

[lazarljubenovic]

I guess leaving it but renaming it is the way to go. At least we'll have a function, which is better than nothing!

[kkirsche]

Rebased against master and I've renamed the function to isPartialRecord, updated the guard and the comment

[kkirsche]

😄 well, at least the github actions workflows are protecting things