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
You may get Child objects with an id but no name, if there was an error in service 2, even though it's a required field.
This seems like it breaks the schema agreement to me. The service is now returning an object without some of the required fields. I think in those failure cases we may need to bubble up the null value to the parent, and so on, until we reach a nullable parent. That would keep to the GQL spec.
The text was updated successfully, but these errors were encountered:
This is a trimmed down copy-pasta of a comment from #99:
We're currently returning partial results for federated objects whose required fields cannot be resolved.
If you have this (psuedo-code) schema in service 1:
and this in service 2:
And run this query:
You may get
Child
objects with anid
but noname
, if there was an error in service 2, even though it's a required field.This seems like it breaks the schema agreement to me. The service is now returning an object without some of the required fields. I think in those failure cases we may need to bubble up the null value to the parent, and so on, until we reach a nullable parent. That would keep to the GQL spec.
The text was updated successfully, but these errors were encountered: