[WIP] Data masking algorithm

[jerelmiller]

This is FAR from done and not ready for any sort of formal review. Throwing this up there to be transparent about progress.

This is in a very rough state and is more of a brute force attempt at this stage. As I make progress, I'll layer in performance enhancements and additional things needed by this algorithm. All fragment data is currently lost when returning from the masking function which will be essential to the end-goal.

[changeset-bot]

⚠️ No Changeset found

Latest commit: dc91836

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[phryneas]

Just out of interest - is there a reason you're not hooking into that as part of the cache, about here?

apollo-client/src/cache/inmemory/readFromStore.ts

Lines 442 to 453 in 1dfd5aa

	const fragment = getFragmentFromSelection(
	selection,
	context.lookupFragment
	);
	if (!fragment && selection.kind === Kind.FRAGMENT_SPREAD) {
	throw newInvariantError(`No fragment named %s`, selection.name.value);
	}
	if (fragment && policies.fragmentMatches(fragment, typename)) {
	fragment.selectionSet.selections.forEach(workSet.add, workSet);
	}