GraphQlError Bug fix

[MathibelaD]

C:\Users\User\Desktop\TICKETING\ticketing\node_modules.pnpm\graphql@16.7.1\node_modules\graphql\error\syntaxError.js:15
return new _GraphQLError.GraphQLError(Syntax Error: ${description}, {
^

GraphQLError: Syntax Error: Expected Name, found "}".
at syntaxError (C:\Users\User\Desktop\TICKETING\ticketing\node_modules.pnpm\graphql@16.7.1\node_modules\graphql\error\syntaxError.js:15:10)
at Parser.expectToken (C:\Users\User\Desktop\TICKETING\ticketing\node_modules.pnpm\graphql@16.7.1\node_modules\graphql\language\parser.js:1397:40)
at Parser.parseName (C:\Users\User\Desktop\TICKETING\ticketing\node_modules.pnpm\graphql@16.7.1\node_modules\graphql\language\parser.js:108:24)
at Parser.parseFieldDefinition (C:\Users\User\Desktop\TICKETING\ticketing\node_modules.pnpm\graphql@16.7.1\node_modules\graphql\language\parser.js:836:23)
at Parser.optionalMany (C:\Users\User\Desktop\TICKETING\ticketing\node_modules.pnpm\graphql@16.7.1\node_modules\graphql\language\parser.js:1492:28)
at Parser.parseFieldsDefinition (C:\Users\User\Desktop\TICKETING\ticketing\node_modules.pnpm\graphql@16.7.1\node_modules\graphql\language\parser.js:822:17)
at Parser.parseObjectTypeExtension (C:\Users\User\Desktop\TICKETING\ticketing\node_modules.pnpm\graphql@16.7.1\node_modules\graphql\language\parser.js:1153:25)
at Parser.parseTypeSystemExtension (C:\Users\User\Desktop\TICKETING\ticketing\node_modules.pnpm\graphql@16.7.1\node_modules\graphql\language\parser.js:1070:23)
at Parser.parseDefinition (C:\Users\User\Desktop\TICKETING\ticketing\node_modules.pnpm\graphql@16.7.1\node_modules\graphql\language\parser.js:208:23)
at Parser.many (C:\Users\User\Desktop\TICKETING\ticketing\node_modules.pnpm\graphql@16.7.1\node_modules\graphql\language\parser.js:1511:26) {
path: undefined,
locations: [ { line: 65, column: 1 } ],
extensions: [Object: null prototype] {}
}

Node.js v18.16.0
[nodemon] app crashed - waiting for file changes before starting...

[MathibelaD]

the error is found in api/src/modules/User/user.graphql line 65,
the empty extend type query is causing the problem however im still not sure why.

when you add a new field, for example

extend type Query {
  goodbye: String!
}

the error is solved.