Async functions for querying public graph

Currently the only way to query the public graph using a specific schema is to go through Hypergraph's client-side useQuery hook. This works well when you need to modify the data, as we can keep the source of truth for queried data in the same place as modified data.

There are some use-cases where you just need to query for public data but not modify it. For this use case useQuery still works, but it won't work for server-side rendering or ad-hoc queries that run as a result of side-effects.

We should expose the query internals in a separate query(Schema) function.

Query options

Queries require things like the mapping or the space in order to generate the query + filters for a specific schema. We'll need a way to provide these options to the query at query time.

Option 1
We can pass the options to the query directly.

await query(Address, { mapping, spaceId })

Option 2
We can create a QueryClient which accepts options. Not entirely sure but this probably looks similar to hypergraph/react's internal context for spaces.

const client = new HypergraphClient({ mapping, spaceId });
await client.query(Address)

Appendix

• https://github.com/graphprotocol/hypergraph/blob/eaa633a8ff2d659da4edd5b5b51071c1a47e517d/packages/hypergraph-react/src/internal/use-query-public.tsx#L384

Commencez par l’implémentation interne liée dans l’annexe, packages/hypergraph-react/src/internal/use-query-public.tsx à la ligne 384, et retracez la façon dont useQuery construit les requêtes de schéma, les mappings, les spaces et les filtres. Comparez les deux conceptions d’options proposées pour fournir mapping et spaceId, puis définissez le point d’entrée de requête asynchrone pour le rendu côté serveur et les requêtes avec effets de bord. La tâche est terminée lorsque les données publiques du graphe peuvent être interrogées sans le hook useQuery de React.