additionalResolvers child field arguments aren't passed through to the backend / all fields are requested

[paales]

We're very happy what GraphQL Mesh is offering! Thanks for the hard work.

Added the following to my .meshrc.json, this does seem to work:

{
  "additionalTypeDefs": "extend type MagentoCategory { category: CategoryTree }",
  "additionalResolvers": [
    {
      "type": "MagentoCategory",
      "field": "category",
      "requiredSelectionSet": "{ url }",
      "targetSource": "Magento GraphQL",
      "targetMethod": "categories",
      "args": { "filters.url_path.eq": "{root.url}", "pageSize": "1" },
      "returnData": "items[0]",
      "resultDepth": 4
    }
  ]
}

To fetch the data I can now do:

query {
  pages(where: { url: "page/home" }) {
    content {
      __typename
      ... on RowProductGrid {
        magentoCategory {
          category {
            url_path
            product_count
            name
            products(pageSize:2) {
              items {
                name
              }
            }
          }
        }
      }
    }
  }
}

What I'd expect:
I'd expect the pageSize: 2 to be passed.

What actually happens:
It doesn't pass the argument and returns too many results

[paales]

Also, it seems that is requesting every field on the planet from the backend instead of only selecting the fields that are requested. I was wondering if this could be cleaned up in some way, as this chokes the backend?

I was already trying to figure out why it was choking when I set the depth to a relatively high value, but that explains it.

I'd expect the backend query to only fetch the fields that are actually requested by the query?

[paales]

@ardatan Maybe I can help with implementing the feature, but I hit a roadblock, maybe you can help a little bit

I can't find any existing tests that test the current additionalResolvers functionality. Maybe you can help me and set up a test?

Maybe a small thing: The additionalResolvers are handled in the config package, doesn't seem the right place for such a functionality?