Type declaration file doesn't get emitted to .mesh when there is no get in yaml file

[gablabelle]

Describe the bug
It might not be the exact reason but it seems like if we don't have a get in the yaml file, the type declaration doesn't get emitted to .mesh

To Reproduce
Steps to reproduce the behavior:

1. Checkout the following branch (type-declaration-emitting-bug) and run yarn install.
2. cd to the packages/graphql-server folder and run yarn build && yarn mesh build. See the output in .mesh contains the index.d.ts type declaration as it should.

3. Now comment line 40 to 49 in src/test.yaml, save the file and run yarn mesh build again. See the output in .mesh does NOT contains the index.d.ts type declaration as it should.

Expected behavior
.mesh/index.d.ts file should be emitted

Environment:

• OS:
  Mac OS 11.4 BigSur

• @graphql-mesh/...:
  @graphql-mesh/cli@0.34.1
  @graphql-mesh/openapi@0.18.7

• NodeJS:
  v14.15.4

[santino]

I think the problem here might be wider and related to the fact that a valid GraphQL schema must have Query fields.

The OpenApi-to-GraphQL library automatically creates GraphQL Query fields from GET endpoints, and Mutation fields from POST endpoints.

If you do not have GET endpoints you will not have Query fields and your GraphQL schema will not be valid.

Apart from explicitly defining some GET endpoints on your OpenApi schema, you can also tell OpenApi-to-GraphQL to treat some of your POST endpoints as Query fields by overriding its default behaviour.

Hope this is of some help.

[gablabelle]

I think the problem here might be wider and related to the fact that a valid GraphQL schema must have Query fields.

The OpenApi-to-GraphQL library automatically creates GraphQL Query fields from GET endpoints, and Mutation fields from POST endpoints.

If you do not have GET endpoints you will not have Query fields and your GraphQL schema will not be valid.

Apart from explicitly defining some GET endpoints on your OpenApi schema, you can also tell OpenApi-to-GraphQL to treat some of your POST endpoints as Query fields by overriding its default behaviour.

Hope this is of some help.

@santino ok but I have queries in the other yaml files (openapi handler too) and inside my custom resolvers too. And this was working before upgrading and using the new API. 🤔

[santino]

Got it.
Probably important to specify to checkout branch type-declaration-emitting-bug.
I did initially check master which was outdated, but following updates seemed to work fine.

You're right, there is something going on.
I noticed that if you remove other data sources and keep only test (even with the removed "get" section) things still work fine.
So the issue seems to be in conjunction with other sources.
Quite strange, cause the schema.graphql artifact is generated and seems correct, so the stitching process is working well.

It needs some debugging for sure.

[badeAdebayo]

any update on this

[ardatan]

I checked out the branch and updated the versions and it looks working fine. Today we don't generate .js and .d.ts files and only .ts file.
We also did bunch of improvements on the CLI. I'd love to get some feedback from your experience with the latest version. Closing this issue for now. Please create a new one if you have any issues with a reproduction on CodeSandbox or StackBlitz or failing test