Non-shareable fields coming from pagination

[cosmin-techoff]

Describe the bug
I get the following errors when trying to create a federation graph:

Non-shareable field "PageInfo.hasNextPage" is resolved from multiple subgraphs: it is resolved from subgraphs "orders" and "shipments" and defined as non-shareable in all of them
Non-shareable field "PageInfo.hasPreviousPage" is resolved from multiple subgraphs: it is resolved from subgraphs "orders" and "shipments" and defined as non-shareable in all of them
Non-shareable field "PageInfo.startCursor" is resolved from multiple subgraphs: it is resolved from subgraphs "orders" and "shipments" and defined as non-shareable in all of them
Non-shareable field "PageInfo.endCursor" is resolved from multiple subgraphs: it is resolved from subgraphs "orders" and "shipments" and defined as non-shareable in all of them

Is there any way to add the directive to this type?

Have you read the Contributing Guidelines?

yes

Expected behavior
PageInfo type should have the @Shareable directive

[tanasievlad246]

@cosmin-techoff have you found a workaround for this issue? I want to use the paging strategy OFFSET, but cant because of this error.

IntrospectAndCompose failed to update supergraph with the following error: A valid schema couldn't be composed. The following composition errors were found:        Non-shareable field "OffsetPageInfo.hasNextPage" is resolved from multiple subgraphs: it is resolved from subgraphs "auctions" and "users" and defined as non-shareable in all of them
        Non-shareable field "OffsetPageInfo.hasPreviousPage" is resolved from multiple subgraphs: it is resolved from subgraphs "auctions" and "users" and defined as non-shareable in all of them

[tanasievlad246]

I anyone is having this issue or is still using this package, go to https://tripss.github.io/nestjs-query/docs/graphql/resolvers/ it is the same but maintained and has some of the features that are mentioned in this issues.

[coupster74]

I’ve been using it for a few years now and the owner is on top of it. Better than a stale library.

…

On Jan 9, 2025, at 4:58 AM, Vlad Tanasie ***@***.***> wrote: I anyone is having this issue or is still using this package, go to https://tripss.github.io/nestjs-query/docs/graphql/resolvers/ it is the same but maintained and has some of the features that are mentioned in this issues. — Reply to this email directly, view it on GitHub <#1566 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABVKEISVSHWOX5IHDW4MVID2JZP45AVCNFSM6AAAAABUX2DTNGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZZHE3TOMJRHE>. You are receiving this because you are subscribed to this thread.