Closed iamkhalidbashir closed 2 years ago
When I close an issue, saying for checking out our Discord channel, or StackOverflow, that means this isn't a bug and yes, I'm sure about this. Please, respect that.
We are using GitHub to track bugs, feature requests, and potential improvements.
Is there an existing issue for this?
Current behavior
Jest e2e tests fail when using globalSetup option I suspect the issue has something to do with circular dependency between Dto files (as shown in the attached Minimum reproduction code)
@kamilmysliwiec Before you close this issue without any reason, please note that I have already posted this issue on discord with no luck, and it has been a month on discord and no one has been able to solve it. It is definitely a bug within the source code in this lib, please have a look
Minimum reproduction code
https://github.com/iamkhalidbashir/nestjs-graphql-jest-error
Steps to reproduce
To reproduce failing tests:-
To check why the tests fail
Expected behavior
Should pass regardless of using globalSetup in jest options or not
Package version
10.1.1
Graphql version
graphql
: 16.6.0apollo-server-express
: 3.10.2apollo-server-fastify
: nullNestJS version
10.1.1
Node.js version
v14.20.0
In which operating systems have you tested?
Other
Logs from the minimum reproduction code (https://github.com/iamkhalidbashir/nestjs-graphql-jest-error)