Working with multiple schemas in the same project

[Xetera]

I'm currently looking for a way to separate the external and internal mutations on my API. Since nexus doesn't do JIT compiling of schemas based on permissions the way https://github.com/hasura/graphql-engine and https://graphql-ruby.org/authorization/visibility.html does, which allows hiding mutations and data types from users without the right permissions when introspecting, is it possible to conveniently generate 2 schemas from the same data source?

If so, are there any examples I can look at? I haven't been able to find much on this topic unfortunately.

[Xetera]

I was able to generate two separate schema outputs from the same codebase using a filtering technique like this that just filters out any object that starts with Private

import * as types from "./resolvers"

const publicTypes = Object.fromEntries(
  Object.entries(types).map(([key, value]) => {
    return [key, Object.fromEntries(
      Object.entries(value).filter(([name]) => !name.toLowerCase().startsWith("private"))
    )]
  })
)

export const schema = makeSchema({
  // ...
  types: publicTypes,
});

export const privateSchema = makeSchema({
  // ...
  types,
});

Inside your resolvers you can declare additional queries/mutations without exposing them like such

// lib/resolvers/user.ts
import { objectType, mutationField } from "nexus";

export const User = objectType({
  name: "User",
  definition(t) {
    t.model.name()
  },
});

export const PrivateMutation = mutationField((t) => {
  t.field("banUser", {
    // ...
  })
})

to split types into separate visibilities you can use extendType on the private version you want to expose internally after your objectType declarations

export const PrivateUser = extendType({
  type: "User",
  definition(t) {
    t.model.address()
  },
});

From there you simply pass privateSchema into the graphql server of your choice and of course disable introspection in production. Hope that can be of use to someone else looking to expose a private graphql schema on top of their public one.