[Bug?] GraphQL Does not Filter Related Collections

Consider a simple Location object containing collection of Links. The links are attached using M2M relationship (I also tested with O2M). When executing a query like the following:

location(id: "/api/location/some_uuid") {
  links {
    edges {
      node {
        id,
        name
      }
    }
  }
}

I get the following output in the profiler:

As you can see the topmost query (4) contains WHERE for the id of location, while 6 counts ALL links and 7 fetches ALL links (not just assigned to the Location). I tried with and without repository defined on the Link entity - the behavior is the same. I’m currently running v2.4.0-beta.1.

Am I doing something wrong or this is a rather scary bug?

[kiler129]

Ok, that was a PEBKAC. This came from the normalizers priority and the fact my custom normalizer was called before GraphQL one and the custom one was composing api_platform.serializer.normalizer.item instead of api_platform.graphql.normalizer.item

[tobyski-tdsultra]

I found this post through google and had exactly the same issue, my related collections were not auto filtered by the parent entity. To fix I just needed to ensure my custom Doctrine serializers included a format check to not run if $format == ‘graphql’.