fix loading handle

[nikgraf]

No description provided.

[Copilot]

Pull Request Overview

This PR refactors how document handles are obtained (migrating from useRepo to a global store selector), adds safety guards around possibly undefined handles in various hooks, and cleans up imports and error logging.

• Switch useSubscribeToSpaceAndGetHandle to use useSelector from the store instead of useRepo
• Add checks for undefined handles in all use*Entity and query hooks, returning throwing stubs or fallbacks
• Remove unused imports and comment out console errors in the App context

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
packages/hypergraph-react/src/HypergraphSpaceContext.tsx	Migrate handle lookup to selector and guard undefined handles in hooks
packages/hypergraph-react/src/HypergraphAppContext.tsx	Consolidate type imports and comment out stray console.error
apps/events/src/components/users.tsx	Remove hardcoded space ID from useCreateEntity call

Comments suppressed due to low confidence (3)

packages/hypergraph-react/src/HypergraphSpaceContext.tsx:8

• The cleanup callback in useSubscribeToSpaceAndGetHandle is currently empty, which may lead to orphaned subscriptions if spaceId or enabled changes. Implement an unsubscribe call there to avoid memory leaks.

  createContext,

packages/hypergraph-react/src/HypergraphSpaceContext.tsx:69

• [nitpick] The hooks use different destructuring names (space vs spaceIdFromParams) across functions, which can be confusing. Consider standardizing on a single parameter name like spaceId for clarity.

  const { space: spaceIdFromParams } = options ?? {};

apps/events/src/components/users.tsx:11

• Removing the explicit space argument changes the hook's behavior to rely on context. Ensure the context always provides the correct space or re-introduce the explicit ID if multi-space usage is expected.

  const createEntity = useCreateEntity(User);

[Copilot]

Commented-out logging can clutter the codebase. Either remove the dead code or re-enable the check with a proper logging strategy and a clear TODO note.

Suggested change

	// console.error(
	// `Received invalid signature, recovered signer is ${signer},
	// expected ${authorIdentity.signaturePublicKey}`,
	// );
	// TODO bring back signature verfication
	// return { valid: false, update: new Uint8Array([]) };
	console.error(
	`Received invalid signature, recovered signer is ${signer}, expected ${authorIdentity.signaturePublicKey}`
	);
	// TODO: Implement signature verification logic here to handle invalid signatures.
	return { valid: false, update: new Uint8Array([]) };