Generating and registering GraphQL schemas dynamically at runtime

[jonwhitty]

I'm trying to build an application backed by mongodb that allows users to create namespaces (backed by mongo collections) and write configurations (backed by mongo documents) under these namespaces. When a client creates a namespace they specify a jsonschema describing the schema(s) that the configuration documents stored within the namespace can have. For example, consider a namespace schema specification like this:

{
    "anyOf": [
        {
            "type": "object",
            "required": ["name"],
            "properties": {
                "name": {
                    "type": "string"
                }
            }
        },
        {
            "type": "object",
            "required": ["hairColor"],
            "properties": {
                "hairColor": {
                    "type": "string"
                }
            }
        }
    ]
}

Configuration documents written to this namespace would have to have a schema structure matching at least one of the object specifications above. This is enforced by using the Schema Validation feature of mongodb.

I'd also like to be able to query these configuration structures using GraphQL. Clients should be able to fetch properties of configuration documents within a namespace matching their GraphQL query. For example:

query {
    configurations(namespaceId: "mynamespace") {
        hairColor
    }
}

the query above would fetch all of the configuration documents that have a hairColor field and return the hairColor properties for that field.

Another example:

query {
    configurations(namespaceId: "mynamespace") {
        hairColor
        name
    }
}

the query above would fetch all of the configuration documents that have a name and a hairColor field and return the hairColor and name fields from them.

When a new namespace is added to the system I'd like to generate a GraphQL schema from the namespace's schema specification and register it at runtime with the GraphQL server so that I can serve queries for configuration documents stored with these namespaces. Any two namespaces might have completely different schemas governing the structure of the configuration documents in that namespace.

Is something like this supported? If so, how do I go about doing that? If not, does the gqlgen community have any suggestions for designing something like this?

I'm looking for something similar to DGS's Dynamic schemas support.