Field level resolver makes the field disappear from TS typegen

Hi. I want to store 1-many relation in an array which contains ids to related objects. orders: [123, 456, 789] And then I want that field level resolver to grab related objects but as soon as i add resolver function the field disappears and TS raises an error saying field does not exist on type. Relevant image: For example having only type: type: list("Order") does not remove the field from TS typegen but as soon as resolve func is added, the field is gone.

What’s the problem here? Am i misunderstanding something?

[tgriesser]

Yeah, this has been a longstanding source of confusion. The original intention of Nexus is that you’re providing a way to resolve your “source types” globally: https://nexusjs.org/docs/guides/source-types#globally-configure-source-types

I use a fork of schemats for this. If source / parent is an object that’s an ORM class, then you’d want a way to know it’s that object and not a vanilla JS object. I use a codegen of the database with a fork of schemats for this, but for simpler types or if you don’t want/need to do this, it should be possible to manage this on the object’s field definition.

I’m thinking maybe we add a convenience helper for this, sourceType?

sourceType: true - preserve sourceType: 'string | number', etc - specify custom typing

t.list.field('orders', {
  type: 'Order',
  sourceType: true,
  resolve: () => // ...
})

If true it will preserve whatever the typing would otherwise be for the field based on the definition, so in this case:

parent.orders // Order[] | null | undefined

@jasonkuhrt thoughts?

[VincentGillot]

Is there any news on this? Because if I use: sourceType: { module: __filename, export: 'UserShape' } The type is correctly imported in the generated types file but since I use this file in the front-end I don’t have access to the import.