relayPagination and network-only

Hi All

I have the following query

query FriendsQuery($after: String!) {
  me {
    id
    friends(after: $after) {
      edges {
        node {
          ...FriendshipFragment
        }
      }
      pageInfo {
        endCursor
        hasNextPage
      }
    }
  }
}

And the following hook

export const useFriends = () => {
  const client = useClient();
  const [{ fetching, error, data }] = useQuery<
    FriendsQueryQuery,
    FriendsQueryQueryVariables
  >({
    query: FRIENDS_QUERY,
    requestPolicy: "network-only",
    variables: {
      after: "",
    },
  });

  const friends =
    data === undefined ? undefined : data?.me?.friends ?? undefined;

  const fetchMore = React.useCallback(
    (cursor: string) => {
      return client
        .query<FriendsQueryQuery, FriendsQueryQueryVariables>(
          FRIENDS_QUERY,
          { after: cursor },
          { requestPolicy: "network-only" }
        )
        .toPromise();
    },
    [client]
  );

  return React.useMemo(
    () => ({
      fetching,
      error,
      friends,
      fetchMore,
    }),
    [fetching, error, friends, fetchMore]
  );

Results are merged using relayPagination

resolvers: {
  User: {
    friends: relayPagination()
  }
}

I have a component that does an infinite scrolling and shows all my friends.

When the component is unmounted and afterwards remounted i would like to fetch again the lists of friends (hence the network-only)

The problem is that due to the relay pagination the friends variable contains all the friends fetched from the previous mount with pageInfo.hasNextPage === false.

The only request that is requested again is the initial with after === “”

Thanks

[zenios]

As for the very specific, I dont think i am the only person who want to use relayPagination with cache-and-network || network-only

[zenios]

Nope i did the merging manually without using relayPagination

On Wed, Jan 20, 2021 at 12:14 PM Vinícius Lemes [e-mail] wrote:

I’m having what I think is the same problem described here. @zenios https://github.com/zenios did you end up finding a solution/workaround?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/FormidableLabs/urql/issues/672#issuecomment-763496418, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAV3YMDTQV6IZBXIBVZ52DS22UJFANCNFSM4LUQKTKA .