Schema must contain uniquely named types but contains multiple types named "EmailObject".
See original GitHub issueHello. There is an error while running api-admin service regarding the EmailObject type. Any possible fixes ?
(node:3244) UnhandledPromiseRejectionWarning: Error: Schema must contain uniquely named types but contains multiple types named "EmailObject".
at new GraphQLSchema (C:\Users\msi4\apps\ultimate-backend\node_modules\graphql\type\schema.js:194:15)
at GraphQLSchemaFactory.<anonymous> (C:\Users\msi4\apps\ultimate-backend\node_modules\@nestjs\graphql\dist\schema-builder\graphql-schema.factory.js:41:32)
at Generator.next (<anonymous>)
at C:\Users\msi4\apps\ultimate-backend\node_modules\@nestjs\graphql\node_modules\tslib\tslib.js:114:75
at new Promise (<anonymous>)
at Object.__awaiter (C:\Users\msi4\apps\ultimate-backend\node_modules\@nestjs\graphql\node_modules\tslib\tslib.js:110:16)
at GraphQLSchemaFactory.create (C:\Users\msi4\apps\ultimate-backend\node_modules\@nestjs\graphql\dist\schema-builder\graphql-schema.factory.js:30:28)
at GraphQLSchemaBuilder.<anonymous> (C:\Users\msi4\apps\ultimate-backend\node_modules\@nestjs\graphql\dist\graphql-schema.builder.js:57:60)
at Generator.next (<anonymous>)
at C:\Users\msi4\apps\ultimate-backend\node_modules\@nestjs\graphql\node_modules\tslib\tslib.js:114:75
at new Promise (<anonymous>)
at Object.__awaiter (C:\Users\msi4\apps\ultimate-backend\node_modules\@nestjs\graphql\node_modules\tslib\tslib.js:110:16)
at GraphQLSchemaBuilder.buildSchema (C:\Users\msi4\apps\ultimate-backend\node_modules\@nestjs\graphql\dist\graphql-schema.builder.js:56:28)
at GraphQLSchemaBuilder.<anonymous> (C:\Users\msi4\apps\ultimate-backend\node_modules\@nestjs\graphql\dist\graphql-schema.builder.js:26:39)
at Generator.next (<anonymous>)
at C:\Users\msi4\apps\ultimate-backend\node_modules\@nestjs\graphql\node_modules\tslib\tslib.js:114:75
(node:3244) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:3244) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Relevant issues https://github.com/MichalLytek/type-graphql/issues/396 https://github.com/nestjs/graphql/issues/721
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Getting "Schema must contain uniquely named types but ...
Hello, I have the following schema: @ObjectType() class Action { @Field(type => Skill, { nullable: true }) skill?
Read more >Error: Schema must contain uniquely named types but ...
This error usually occurs if you have named two or more of your Object Types with the same name . For example,
Read more >Error: Schema must contain uniquely named types but ...
Hello, see GitHub issue here: Error: Schema must contain uniquely named types but contains multiple types named "DateTime".
Read more >Error: Schema Must Contain Uniquely Named ... - ADocLib
A GraphQL object type has a name and fields but at some point those fields have to resolve to some concrete data.That's where...
Read more >Oracle® SQL Developer - Data Modeler User's Guide
Derivative Works shall not include works that remain separable from, or merely link (or ... The data types model in Data Modeler combines...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Done 😃
Found it ! 😄 Turned out very simple. There are duplicate GraphQLModule imports.