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 panic approach to treat cases when a Gqlgen related context is missing can cause unexpected issues when you have some helper func depending on one of the contexts to do something.
i.e. in our case, we have some helper functions that use the AddError and GetErrors but have no way to check if HasResponseContext similar to how we check if HasOperationContext based on the current API.
What did you expect?
Have a function HasResponseContext to be able to check if it exists and prevent panic if it does not in code using gqlgen funcs that require the Response Context to exist.
Minimal graphql.schema and models to reproduce
N/A
versions
the main branch still does not have a way to check if Response Context exists.
The text was updated successfully, but these errors were encountered:
What happened?
The
panic
approach to treat cases when a Gqlgen related context is missing can cause unexpected issues when you have some helper func depending on one of the contexts to do something.i.e. in our case, we have some helper functions that use the
AddError
andGetErrors
but have no way to check ifHasResponseContext
similar to how we check ifHasOperationContext
based on the current API.What did you expect?
Have a function
HasResponseContext
to be able to check if it exists and preventpanic
if it does not in code using gqlgen funcs that require the Response Context to exist.Minimal graphql.schema and models to reproduce
N/A
versions
Response Context
exists.The text was updated successfully, but these errors were encountered: