Open slavikovbasa opened 3 months ago
So basically we need to error propagation mechanism in denormalization ?
not sure if denormalization is the best place to do it, maybe somewhere after parsing?
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.