`useResult` suspends when returnig components

[PatrykWalach]

Should it not suspend, but return components that suspend when rendered?

prerequisite:

• ReaderArtifact contains field name needed to store the component, it might need to be moved.

[rbalicki2]

I agree. useResult of an @component should never suspend

[PatrykWalach]

@rbalicki2 for this to work, I have to know if FragmentReference points to component or field upfront and have the fieldName to cache the component, so I'd need to add readerKind and fieldName to ReaderWithRefetchQueriesLoader

isograph/libs/isograph-react/src/core/entrypoint.ts

Lines 20 to 28 in 6ca0df8

	export type ReaderWithRefetchQueriesLoader<
	TReadFromStore extends UnknownTReadFromStore,
	TClientFieldValue,
	> = {
	readonly kind: 'ReaderWithRefetchQueriesLoader';
	readonly loader: () => Promise<
	ReaderWithRefetchQueries<TReadFromStore, TClientFieldValue>
	>;
	};

and then copy them to FragmentReference

isograph/libs/isograph-react/src/core/FragmentReference.ts

Lines 47 to 64 in 6ca0df8

	export type FragmentReference<
	TReadFromStore extends UnknownTReadFromStore,
	TClientFieldValue,
	> = {
	readonly kind: 'FragmentReference';
	readonly readerWithRefetchQueries: PromiseWrapper<
	ReaderWithRefetchQueries<TReadFromStore, TClientFieldValue>
	>;
	readonly root: StoreLink;
	// TODO we potentially stably copy and stringify variables a lot!
	// So, we should employ interior mutability: pretend that fragent reference
	// is immutable, but actually store something like
	// `Map<Variable, StablyCopiedStringifiedOutput>`
	// and read or update that map when we would otherwise stably copy and
	// stringify.
	readonly variables: ExtractParameters<TReadFromStore>;
	readonly networkRequest: PromiseWrapper<void, any>;
	};

This just doesn't feel right to me, because data is duplicated. I don't know what's the best way to model this.