Open nathan-king opened 4 years ago
Windows and WLS2/Ubuntu
1.7.23
Schema would update in playground afterupdating schema.ts file and the schema would only reflect the current project.
Schema doesn't update. Scalars defined in previous projects are appearing. Schema is carrying on from Windows projects into WSL2 projects...
Up to step 5.3 in this URL using WSL2 (nexus not available on Windows) :
https://dev.to/prisma/complete-introduction-to-fullstack-type-safe-graphql-feat-next-js-nexus-prisma-c5
The problem occurred while using nexus and Apollo, my Apollo project where I came across the bug first was using Windows
Please provide a gif or image of the issue for a quicker response/fix.
My files:
Meant to look like this:
This issue pertains to the following package(s):
What OS and OS version are you experiencing the issue(s) on?
Windows and WLS2/Ubuntu
What version of graphql-playground(-electron/-middleware) are you experiencing the issue(s) on?
1.7.23
What is the expected behavior?
Schema would update in playground afterupdating schema.ts file and the schema would only reflect the current project.
What is the actual behavior?
Schema doesn't update. Scalars defined in previous projects are appearing. Schema is carrying on from Windows projects into WSL2 projects...
What steps may we take to reproduce the behavior?
Up to step 5.3 in this URL using WSL2 (nexus not available on Windows) :
https://dev.to/prisma/complete-introduction-to-fullstack-type-safe-graphql-feat-next-js-nexus-prisma-c5
The problem occurred while using nexus and Apollo, my Apollo project where I came across the bug first was using Windows
Please provide a gif or image of the issue for a quicker response/fix.
My files:
Meant to look like this: