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
Just wondering what the best way to abort multiple mutations in a single graphql call, currently I have moved the following code :
if h.resultCallbackFn != nil {
h.resultCallbackFn(ctx, ¶ms, result, buff)
}
To just after the line : result := graphql.Do(params)
This way I can verify if all the mutations supplied to the graphql endpoint have been saved to the database and passes any extra validation as required for our business logic, if this fails, I am able to here fail the entire set of mutations.
Would prefer to use the library "as is" without modifying it, as I assume you guys are the ones in the know what is right and wrong with using this library, do you recommend a better solution, or have a done an acceptable solution ?
Thanks in advance
Cheers
Jason
The text was updated successfully, but these errors were encountered:
Hi,
Just wondering what the best way to abort multiple mutations in a single graphql call, currently I have moved the following code :
if h.resultCallbackFn != nil {
h.resultCallbackFn(ctx, ¶ms, result, buff)
}
To just after the line : result := graphql.Do(params)
This way I can verify if all the mutations supplied to the graphql endpoint have been saved to the database and passes any extra validation as required for our business logic, if this fails, I am able to here fail the entire set of mutations.
Would prefer to use the library "as is" without modifying it, as I assume you guys are the ones in the know what is right and wrong with using this library, do you recommend a better solution, or have a done an acceptable solution ?
Thanks in advance
Cheers
Jason
The text was updated successfully, but these errors were encountered: