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
Such a query is possible and results in a ValueError being thrown:
{
longStub(id:"asdf")
}
It is possible to catch errors in parse/serialize methods of Scalar, but there is no way to return any validation errors to a client.
Would be nice to have either:
Custom error that can be thrown from serialization methods and process it in hiku accordingly;
Or a separate validation method for Scalar
Possibly there is the same problem with enums, haven't checked though.
The text was updated successfully, but these errors were encountered:
Yep, in case when we are parsing arguments we should catch parse errors and report them to user.
My msg about denormalization makes sense when we are serializing scalars. Also being able to report errors from denormalization phase needed for another case when value completion failed (because of null in not-nullable field) and we need to tell user that there is an error.
Having a scheme:
Such a query is possible and results in a ValueError being thrown:
It is possible to catch errors in
parse/serialize
methods ofScalar
, but there is no way to return any validation errors to a client.Would be nice to have either:
Scalar
Possibly there is the same problem with enums, haven't checked though.
The text was updated successfully, but these errors were encountered: