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
I think the current design is pretty flexible and can be used like a pre-request hook which solves at least all my problems like validation.
However, I am thinking of a continueParsing mode to the current design.
So instead of returning whatever returned from the serverless or remote call, what about sometimes I want to reconstruct the query, like, after doing some process, I want to return another set of data instead:
something like I send another graphql query to hasura along with a flag,
then hasura sees the flag,
it will execute the query and return the result to client
so it can save one roundtrip.
@coco98 said I should embed this info as well which I have no idea:
"vis a vis the query root in mutation issue"
The text was updated successfully, but these errors were encountered:
Discuss with @coco98 in Discord before
I think the current design is pretty flexible and can be used like a pre-request hook which solves at least all my problems like validation.
However, I am thinking of a continueParsing mode to the current design.
So instead of returning whatever returned from the serverless or remote call, what about sometimes I want to reconstruct the query, like, after doing some process, I want to return another set of data instead:
@coco98 said I should embed this info as well which I have no idea:
"vis a vis the query root in mutation issue"
The text was updated successfully, but these errors were encountered: