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
Im experiencing some inconsistent behaviour when using client resolvers with Server Edges.
Components which are provided fragments can be observed to not have data they are requesting.
The issue appears to be when using Server Edges in combination with fragments. The client edge query is only actioned when the data is requested in the field with the @waterfall directive is not available in the store. If that field uses a fragment, data within the fragment is not requested if it is not in the store.
It appears that the fragment data is not inspected when making client edge requests
The text was updated successfully, but these errors were encountered:
jonreading81
changed the title
Client Resolvers inconsistent behaviour when using fragments
Client Resolvers with Server edges are not making client edge requests
Mar 11, 2025
Im experiencing some inconsistent behaviour when using client resolvers with Server Edges.
Components which are provided fragments can be observed to not have data they are requesting.
The issue appears to be when using Server Edges in combination with fragments. The client edge query is only actioned when the data is requested in the field with the
@waterfall
directive is not available in the store. If that field uses a fragment, data within the fragment is not requested if it is not in the store.For example a query referencing a fragment with:
In this example the owner.displayName does not trigger an client edge query. However if it was written as below it would:
It appears that the fragment data is not inspected when making client edge requests
The text was updated successfully, but these errors were encountered: