Andrew Obrigewitsch

@jamesguan The problem is that the Context file should be the ts type definition for the context. This enables auto completion and code checking, which makes life much easier. It's...

Seems like you could just wrap all the Types in different client names. Or append something to the front of of each type to mach the DB name. There's many...

I'm using the Nexus-Prisma-Plugin, that outputs a schema, so I then create a second file structure with the second client and merge them together. I think it would be better...

No, it all works, you just have a file for each client that outputs all the generated types. It's pretty hard to explain without a code example. I will see...

I'm having the same issue, what's strange is I've created multiple servers before and never had this issue. So I'm not sure what's causing it. I'm just trying to get...

I think the issue was caused by not running: ```bash ts-node-dev --transpile-only --respawn src/ ``` I didn't have the --transpile-only and that will do it.

I'm using a custom location for storing the client. The client works but when I try to add it to nexus I get the same error. Here's the versions I'm...

This is preventing my from running "tsc build".

I figured out the issue and solution, UserV2 is in the service so I just needed to change the code to this: ```js const federatedSchema = applyMiddleware( transformSchemaFederation(schema, { Query:...

I'm trying to test my Nexus API, and have been looking or hours on ways to do this. We have existing tests from our old schema first API that uses...