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 love coercing ShapeType. I can easily check if given payload is in expected format. However debugging complex ShapeType CoercionException is pain in the ass.
I love coercing ShapeType. I can easily check if given payload is in expected format. However debugging complex ShapeType CoercionException is pain in the ass.
Let's see simple (complex) example:
This will throw
CoercionException
with message:Could not coerce "string" to type "non-empty-string".
It is really confusing I do not know which node is invalid.
I would suggest message like:
Could not coerce (response->object1->code) "string" to type "non-empty-string".
The text was updated successfully, but these errors were encountered: