Runtime schema differs from generated schema in production

[Zn4rK]

Issue workflow progress

Progress of the issue based on the Contributor Workflow

• 1. The issue provides a reproduction available on CodeSandbox.
• 2. A failing test has been provided
• 3. A local solution has been provided
• 4. A pull request is pending review

---

Describe the bug

The expected runtime schema works in mesh dev but not mesh build && mesh start. It seems like the type name is inferred from the field name rather than from the name in the schema.

The generated SDL and TypeScript files are correct and looks like what I would expect. Running mesh dev also yields the correct runtime schema.

The issue only occurs whenever mesh uses the generated jsonSchemaBundle. I don't know if the problem originates here though.

To Reproduce
Steps to reproduce the behavior: repro.

Run "yarn start" and in Playground look at the introspected schema:

Now run yarn prod and again look at the introspected schema:

Expected behavior

I expect it to behave like it does in mesh dev.

Environment:

• OS: MacOS Montery 12.6
• @graphql-mesh:

    "@graphql-mesh/cli": "0.79.3",
    "@graphql-mesh/openapi": "0.33.34",
    "@graphql-mesh/runtime": "0.44.31",

• NodeJS: v16.15.1

Additional context

The Thing type is duplicated and exists twice in the schema.
It does remind me of this issue I filed in openapi-to-graphql.