Skip to content

Client Resolvers with Server edges are not making client edge requests #4882

@jonreading81

Description

@jonreading81

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:

query PlayerQuery {
   items {
      cloudcast @waterfall {
        id,
        ...PlayerItem
      }
  } 
}
fragment PlayerItem_cloudcast on cloudcast {
  name
  owner{
     displayName
   }
}

In this example the owner.displayName does not trigger an client edge query. However if it was written as below it would:

query PlayerQuery {
   items {
      cloudcast @waterfall {
        id,
        owner{
          displayName
        }
        ...PlayerItem
      }
  } 
}

It appears that the fragment data is not inspected when making client edge requests

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions