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
shipment_manifest is backed by a regular old Postgres table with two columns. This should never fail, and if it does I have no intelligent way of handling it in the client.
Exporting my Hasura instance's GraphQL metadata and feeding it through dotansimha/graphql-code-generator using the plugin typescript-graphql-request I get the following:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Consider the following GraphQL:
shipment_manifest
is backed by a regular old Postgres table with two columns. This should never fail, and if it does I have no intelligent way of handling it in the client.Exporting my Hasura instance's GraphQL metadata and feeding it through dotansimha/graphql-code-generator using the plugin
typescript-graphql-request
I get the following:Note that
insert_shipping_manifest
is both optional and aMaybe
. I don't want this for a mutation that "can't possibly fail".Do I need to address this at the use site or is there a way to prevent this issue?
Beta Was this translation helpful? Give feedback.
All reactions