You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The 'magic' handling / recursing logic in the GraphQL connector module's connection.ts interferes with any other Holochain modules which could conceivably be bound to a thirdparty resolver; if those modules are expecting EntryHashB64 or ActionHashB64 as arguments. In these cases the encoding logic will interfere and deserialize such string values to a Uint8Array prior to transmission through @holochain/client.
Fixing this would mean updating @valueflows/vf-graphql-holochain to handle encoding of specific fields (id & revisionId for most record types, plus other 'foreign key' identifiers); rather than the current recursive field detection and de/serialization.
A side-benefit is this would actually make the connection logic quite a bit faster, if slightly more heavyweight in terms of byte size.
The text was updated successfully, but these errors were encountered:
The 'magic' handling / recursing logic in the GraphQL connector module's
connection.ts
interferes with any other Holochain modules which could conceivably be bound to a thirdparty resolver; if those modules are expectingEntryHashB64
orActionHashB64
as arguments. In these cases the encoding logic will interfere and deserialize such string values to aUint8Array
prior to transmission through@holochain/client
.Fixing this would mean updating
@valueflows/vf-graphql-holochain
to handle encoding of specific fields (id
&revisionId
for most record types, plus other 'foreign key' identifiers); rather than the current recursive field detection and de/serialization.A side-benefit is this would actually make the connection logic quite a bit faster, if slightly more heavyweight in terms of byte size.
The text was updated successfully, but these errors were encountered: