Roman Ivantsov
Roman Ivantsov
question - when we use * in a query, how deep it is supposed to go, for fields that return objects or lists of objects?
but then, there might be circular refs in object types. ParentObj has a list of child objects, and child has a ref to parent. You are in infinite loop
can you please explain more? with an example, of query with * , against types with circular refs?
I would side with @ollydixon His case is legit - I guess the client app loads ALL stuff, and turns it into object graph, and then operates it, shows in...
on the second thought, what would happen with Union-type field? of list of union objects? - we might get varying list of fields, even in one array of objects...
@PascalSenn - well, it means fields with params (methods) are excluded, anyway. So this * applies only to fields of primitive types, scalars, enums, or arrays of these. Still, seems...
> This is mildly annoying because now I need a client-side transform to change the enum value into the more common letter grade format (A+, A-, etc.). There is a...
in my opinion, confusing as hell, this intersection thing. Seriously, after reading spec PR, I don't get it, completely, what is that
well, links get obsolete over time - that's understandable. But in this case, it's at time of spec publishing. Better be updated i think
regarding recursive refs in fragments, this is under discussion: https://github.com/graphql/graphql-spec/issues/929 by the way, in the sample, did you mean "...Node" as fragment spread? ```graphql fragment Node on TreeNode { label...