Resolvers composition not working as described in the docs

[gtuk]

Issue workflow progress

Progress of the issue based on the Contributor Workflow

• 1. The issue provides a reproduction available on Github, Stackblitz or CodeSandbox

Make sure to fork this template and run yarn generate in the terminal.

Please make sure Mesh package versions under package.json matches yours.

• 2. A failing test has been provided
• 3. A local solution has been provided
• 4. A pull request is pending review

---

Describe the bug

If i try to use resolversComposition it is not working as expected and my console.log inside the composer is not called.

To Reproduce
Steps to reproduce the behavior:

git clone [email protected]:gtuk/graphql-mesh-resolvers-composition-sample-repo.git
cd graphql-mesh-resolvers-composition-sample-repo.git
yarn dev

Run any query e.g query {capsules {id}}
Expected behavior

If i call any query e.g query {capsules {id}} is not showing the console log from the src/add-fields composer

Environment:

• OS: Linux Mint 20.3
• "@graphql-mesh/cli": "0.78.24"
• "@graphql-mesh/graphql": "0.31.17"
• "@graphql-mesh/transform-resolvers-composition": "0.12.94"
• "graphql": "16.6.0"
• NodeJS: v14.17.3 and v16.17.1

[ardatan]

Resolvers Composition doesn't work with GraphQL handler because the gateway forwards the request to the source without applying a resolution logic.

[gtuk]

Thanks or the info. Seem i missed it completely or the docs don't mentioned it.
Is there anything similar that i can use instead when the handler is graphql?