Error when upgrading to versions beyond 0.94.x releases

[jamesmmchugh]

I didn't want to raise this as an issue, as i'm not sure it's an actual bug. When I upgrade to use the latest version of the cli/graphql mesh packages I run into the following exception whenever I try to build my gateway (which works on core/handler/transform packages <=0.94.x):

 💡 🕸️  Mesh Generating the unified schema
 🐛 🕸️  Mesh - GetMesh Getting subschemas from source handlers
 🐛 🕸️  Mesh - User Generating the schema
 🐛 🕸️  Mesh - Post Generating the schema
 💥 🕸️  Mesh - User Failed to generate the schema GraphQLError: Syntax Error: Unexpected Name "_Any".
     at syntaxError (/work/node_modules/.pnpm/graphql@16.8.1/node_modules/graphql/error/syntaxError.js:15:10)
     at Parser.unexpected (/work/node_modules/.pnpm/graphql@16.8.1/node_modules/graphql/language/parser.js:1458:41)
     at Parser.parseDefinition (/work/node_modules/.pnpm/graphql@16.8.1/node_modules/graphql/language/parser.js:212:16)
     at Parser.many (/work/node_modules/.pnpm/graphql@16.8.1/node_modules/graphql/language/parser.js:1511:26)
     at Parser.parseDocument (/work/node_modules/.pnpm/graphql@16.8.1/node_modules/graphql/language/parser.js:122:25)
     at parse (/work/node_modules/.pnpm/graphql@16.8.1/node_modules/graphql/language/parser.js:32:17)
     at getSubschemaForFederationWithTypeDefs (/work/node_modules/.pnpm/@graphql-tools+federation@1.1.10_@types+node@10.17.60_graphql@16.8.1/node_modules/@graphql-tools/federation/cjs/gateway.js:131:106)
     at GraphQLHandler.getMeshSource (/work/node_modules/.pnpm/@graphql-mesh+graphql@0.96.0_@graphql-mesh+cross-helpers@0.4.1_@graphql-mesh+store@0.96.0_@gr_vq3kogl5232gworyh5a7xoe53q/node_modules/@graphql-mesh/graphql/cjs/index.js:258:88)
     at async /work/node_modules/.pnpm/@graphql-mesh+runtime@0.97.0_@graphql-mesh+cross-helpers@0.4.1_@graphql-mesh+types@0.96.0_@gr_ms6frl3z65btqntugkmlgfov4y/node_modules/@graphql-mesh/runtime/cjs/get-mesh.js:117:28
     at async Promise.allSettled (index 0)
 💥 🕸️  Mesh - Post Failed to generate the schema GraphQLError: Syntax Error: Unexpected Name "_Any".
     at syntaxError (/work/node_modules/.pnpm/graphql@16.8.1/node_modules/graphql/error/syntaxError.js:15:10)
     at Parser.unexpected (/work/node_modules/.pnpm/graphql@16.8.1/node_modules/graphql/language/parser.js:1458:41)
     at Parser.parseDefinition (/work/node_modules/.pnpm/graphql@16.8.1/node_modules/graphql/language/parser.js:212:16)
     at Parser.many (/work/node_modules/.pnpm/graphql@16.8.1/node_modules/graphql/language/parser.js:1511:26)
     at Parser.parseDocument (/work/node_modules/.pnpm/graphql@16.8.1/node_modules/graphql/language/parser.js:122:25)
     at parse (/work/node_modules/.pnpm/graphql@16.8.1/node_modules/graphql/language/parser.js:32:17)
     at getSubschemaForFederationWithTypeDefs (/work/node_modules/.pnpm/@graphql-tools+federation@1.1.10_@types+node@10.17.60_graphql@16.8.1/node_modules/@graphql-tools/federation/cjs/gateway.js:131:106)
     at GraphQLHandler.getMeshSource (/work/node_modules/.pnpm/@graphql-mesh+graphql@0.96.0_@graphql-mesh+cross-helpers@0.4.1_@graphql-mesh+store@0.96.0_@gr_vq3kogl5232gworyh5a7xoe53q/node_modules/@graphql-mesh/graphql/cjs/index.js:258:88)
     at async /work/node_modules/.pnpm/@graphql-mesh+runtime@0.97.0_@graphql-mesh+cross-helpers@0.4.1_@graphql-mesh+types@0.96.0_@gr_ms6frl3z65btqntugkmlgfov4y/node_modules/@graphql-mesh/runtime/cjs/get-mesh.js:117:28
     at async Promise.allSettled (index 1)

I'm using the following packages:

pnpm add @graphql-mesh/cli@0.88.0 graphql
pnpm add @graphql-mesh/graphql@0.96.0
pnpm add @graphql-mesh/transform-type-merging@0.96.0

I'm not doing anything particuarily complicated and am using the following meshrc and schemas:

serve:
  hostname: 0.0.0.0
  playground: true
  cors:
    origin: "*"
sources:
  - name: User
    handler:
      graphql:
        source: user.graphqls
    transforms:
      - typeMerging:
          queryFields:
            - queryFieldName: fixtureSearch
  - name: Post
    handler:
      graphql:
        source: post.graphqls

scalar DateTime
scalar Long

directive @oneOf on INPUT_OBJECT | FIELD_DEFINITION
directive @connection(for: String) on FIELD_DEFINITION
directive @merge(argsExpr: String, keyArg: String, keyField: String, key: [String!], additionalArgs: String) on FIELD_DEFINITION
directive @key(selectionSet: String!) on OBJECT
directive @computed(selectionSet: String!) on FIELD_DEFINITION
directive @canonical on OBJECT | INTERFACE | INPUT_OBJECT | UNION | ENUM | SCALAR | FIELD_DEFINITION | INPUT_FIELD_DEFINITION

type User {
    id: ID!
    username: String!
    email: String!
}

type Query {
    user(id: ID!): User! @merge(keyField: "id") @canonical
}

scalar DateTime
scalar Long

directive @oneOf on INPUT_OBJECT | FIELD_DEFINITION
directive @connection(for: String) on FIELD_DEFINITION
directive @merge(argsExpr: String, keyArg: String, keyField: String, key: [String!], additionalArgs: String) on FIELD_DEFINITION
directive @key(selectionSet: String!) on OBJECT
directive @computed(selectionSet: String!) on FIELD_DEFINITION
directive @canonical on OBJECT | INTERFACE | INPUT_OBJECT | UNION | ENUM | SCALAR | FIELD_DEFINITION | INPUT_FIELD_DEFINITION

type Post {
    id: ID!
    message: String!
    author: User
}

type User {
    id: ID!
    posts: [Post]
}

type Query {
    post(id: ID!): Post
    users(ids: [ID!]!): [User]! @merge(keyField: "id")
}

Any ideas on why this is happening or how I resolve it?

[ardatan]

Could you create a reproduction on CodeSandbox?

[jamesmmchugh]

https://codesandbox.io/p/sandbox/youthful-water-jn3hk7

[jamesmmchugh]

I intended to use the mock plugin for the actual sources, but regardless of if I add it or not I still get the same problem, so at the moment there is no endpoint defined.

[jamesmmchugh]

I also have an additional question; which is why are is the typeMerging transform still required to be defined when all the information necessary is already available by directives. On my working version (using 0.94.x), if I remove the transform definition from the meshrc.yaml file then it no longer federates the calls to the services. This seems to be the same with the federation directives also (replacing the typeMerge tranform with the federation one).

[jamesmmchugh]

I see a similar issue has just recently been created: #6254, i'll keep track there if you want to close this off?

It would be great to get an answer to the question in my response above though. Thanks.