Example of having resolvers in separate files

[prismake]

Example of having resolvers in separate files

[pie6k]

Exactly for reason you've described, single schema can have multiple schema roots.

Example:

import { SchemaRoot, Query, Mutation, compileSchema } from "typegql";

@SchemaRoot()
export class UserSchemaRoot {
  @Query()
  allUsers() {}
}

@SchemaRoot()
export class UserMutationsSchemaRoot {
  @Mutation()
  registerUser() {}
}

@SchemaRoot()
export class ProductSchemaRoot {
  @Query()
  allProducts() {}
}

const finalSchema = compileSchema([UserSchemaRoot, UserMutationsSchemaRoot, ProductSchemaRoot])

As seen, final schema is composed from many 'root' classes. Obviously, those classes can be defined in different files and imported.

Technically, you're not importing resolver itself, but you're able to divide your schema logic into many parts and it'd scale horizontally even for huge schema allowing you to have many small, easy to understand files.

Let me know if that solves your problem.

I would also like to know this as well. We want to define our schemas in one package that also our consumers use. Then define the resolvers in our private server code. If that's at all possible.

[capaj]

I don't know if I am not missing something, but you certainly can have a SchemaClass which exposes your internal class.
So:

const myUberPrivateSchema = {
  a() {...}
}

// somewhere else
@SchemaRoot()
export class Schema { 
  @Mutation()
  public a() {
    return myUberPrivateSchema.a()
  }
}

[jdolle]

Works for my purposes. Thanks