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
Here the UserFragment is forwarded to registration and registration returns an object containing the keys { id name email school }, but GraphQL expects school to be named question so it can itself rename it to school. This is a little more tricky since one must first find which aliases map to which fields and then when multiple aliases for the same thing are in place it has to remember all of them somehow (because they can't be returned all at once, GraphQL will repeatedly call the method with the different alias variants). This could probably be done by some smart caching of the query to the results, then removing the cache when all the results have been returned.
The text was updated successfully, but these errors were encountered:
Currently aliasing in a forwarded query does not work well:
Here the
UserFragment
is forwarded to registration and registration returns an object containing the keys{ id name email school }
, but GraphQL expectsschool
to be namedquestion
so it can itself rename it toschool
. This is a little more tricky since one must first find which aliases map to which fields and then when multiple aliases for the same thing are in place it has to remember all of them somehow (because they can't be returned all at once, GraphQL will repeatedly call the method with the different alias variants). This could probably be done by some smart caching of the query to the results, then removing the cache when all the results have been returned.The text was updated successfully, but these errors were encountered: