Selection set as string or DocumentNode

[jbhurruth]

I'm using the @neo4j/graphql library which features an ORM-style tool call the OGM which shares the augmented schema and generated resolvers with a GraphQL API. The OGM uses the same selection set syntax as GraphQL but without the top level resolver calls, e.g.

const result = await ogm.model('User').find({
      where: { id },
      selectionSet: `{ first_name last_name email address { postcode } }`,
});

I'd like to be able to build these selection sets with Zeus and extend the OGM types to pass through the Zeus generated types.
@aexol, is there a way to get a string or DocumentNode for a Selector without building a full query and then trying to split out the selection set?

[aexol]

There is a function for type which is FromSelector
Maybe combine
TypedDocumentNode<FromSelector
?

[jbhurruth]

That may help with the typing side of things if I was to build the query and split out the selection set but I was hoping I wouldn't have to infer the top level resolver names at runtime.

I essentially want something similar to the typedGql function but that can take a Model name instead of an operation name and return a function that still returns a TypedDocumentNode of the selection set and not the full query.

I'll dig through the Zeus code at some point to figure out how the translation works but for now we've just been using strings everywhere.