fix: Allow readFragment() to accept fragment document as a generic

[kitten]

Note

It's debatable whether this is a feature or a fix, but since it's a relatively safe addition that complements #98 (for #77) and that we can safely roll back if needed, I'd like to try shipping this as a patch to evaluate this quickly.

Summary

This allows the document in readFragment to be passed as a generic, removing the need to keep fragments around as a runtime value.

// previous:
const unmaskedData = readFragment(document, maskedData);
// new:
const unmaskedData = readFragment<typeof document>(maskedData);

Replacing readFragment's complex type argument and data generic with an overload is long and wordy, but potentially makes it simpler for TypeScript to evaluate and prevents us having to maintain mirrorTypeRec.

In case this is needed, we can add its definition back to the overload, but this wouldn't be compatible with being able to pass just one generic for the document.

Set of changes

• Replace maskFragments and readFragment definitions with overloads
• Allow readFragment to only accept one argument

[changeset-bot]

🦋 Changeset detected

Latest commit: e0e4f7a

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR