Binds Holochain cell connections for hREA to a GraphQLClient interface for connecting to distributed, agent-centric ValueFlows coordination spaces.
Simply await the results of this asynchronous function to get a handle on a hREA collaboration space.
In a Svelte application, simple app initialisation logic for connecting to one collaboration space might look something like this:
<script>
import { setClient } from 'svelte-apollo'
import initGraphQLClient from '@vf-ui/graphql-client-holochain'
import App from './my-happ-ui'
// define connection params
const conductorUri = process.env.REACT_APP_HC_CONN_URL || 'ws://localhost:4001'
const dnaConfig = {
// :TODO: determine appropriate `CellId`s by interrogating admin websocket
}
// init and manage GraphQL client connection
let client = null
let loading = true
let error = null
async function initConnection(opts) {
try {
client = await initGraphQLClient(opts)
} catch (e) {
error = e
}
loading = false
error = null
}
initConnection({
conductorUri,
dnaConfig,
})
// workaround to set the context outside of init action
$: {
if (client) {
setClient(client)
}
}
</script>
<main>
{#if loading}
<h1>Loading...</h1>
{:else if error}
<h1>Cannot connect to Holochain</h1>
<p>{error.message}</p>
{:else}
<App />
{/if}
</main>Note that you can connect to multiple conductors and sets of Holochain DNAs in order to naively connect to multiple collaboration spaces; and you can also connect to other non-Holochain ValueFlows-compatible GraphQL client APIs in order to manage data across contexts. In reactive UI applications built with frameworks like React, Svelte etc this means that you can simply swap out the active GraphQLClient with another by wrapping UI elements in a different connection provider in order to target different networks.
TODO: provide an example of this
Options to the function exported by this module are the same as to @valueflows/vf-graphql-holochain.
Licensed under an Apache 2.0 license.