GraphQL support: Issue on pagination

[vico-gs]

Hello there, When using graphQL with api platform 3.0, I noticed something that has changed between 2.6 and 3.0, if have two entities (salad, banana) linked by a ManyToOne relation if the paginationType is page (in salad) and paginationType is cursor (in banana)
When we fetch a banana with simple query:

query 
{
 bananas { totalCount }
}

the cursor pagination works well ! The type of the banana connection is called BananaCursorConnection. BUT when the collection is called inside another query

query
{
 salad
 {
  bananas
  {
   totalCount
  }
 }
}

It will not work and return the error that totalCount is not a correct attribute.
Actually it seems that the type of the bananas has strangely turned into BananaPageConnection forced by the primary entity called.

I tried to force the type by using a TypeConverter which returned me a BananaCursorConnectionPageConnection ....

Is it a correct behavior for api_platofrm 3.0 or did I miss a configuration somewhere ?
Thanks !

[vico-gs]

Ok so I tried something, I added to the salad annotations in the ApiResource the following parameter, with the pagination to cursor:

graphQlOperations: [ new Query(paginationType: 'cursor', name: "item_query") ]

It seems that the parent of the collection force the paginationType of it's child.

Because I was then able to do the following graphQL query:

query
{
 salad
 {
  bananas
  {
   totalCount
  }
 }
}

And it worked like a charm.

[xavierleune]

Hello, should this issue be closed (cf PR #5102) ?

[soyuka]

Resolved: src/GraphQl/Type/FieldsBuilder.php now derives the operation from the nested resource's own metadata (its collection_query/item_query) rather than the parent root operation, so child pagination type is used. Verified on current 4.3 HEAD. Closing as fixed.