Combination of "expose" and GraphQL JIT can cause a resolve failure

Hello,

I have found a problem when using "expose" and GraphQL JIT. I have following example, that is correctly compiled by typescript:

import { createYoga } from 'graphql-yoga';
import { createServer } from 'node:http';
import SchemaBuilder from '@pothos/core';
import { useGraphQlJit } from '@envelop/graphql-jit'

const builder = new SchemaBuilder({ });

class User {
    name: Promise<string>;
    constructor() {
        this.name = Promise.resolve('name');
    }
}

builder.objectType(User, {
    name: 'User',
    fields: (t) => ({
        name: t.exposeString('name'),
    }),
})

builder.queryType({
    fields: (t) => ({
        user: t.field({
            type: User,
            resolve: () => new User(),
        }),
    }),
});

const yoga = createYoga({
    schema: builder.toSchema(),
    plugins: [useGraphQlJit()],
});

const server = createServer(yoga);

server.listen(3000, () => {
    console.log('Visit http://localhost:3000/graphql');
});

I'm trying query

query {
  user {
    name
  }
}

When JIT is not in plugins, I get correct response. When I use JIT, I see error String cannot represent value: {}. Because the name is Promise.

In Readme of JIT there is: "The primary limitation is that all computed properties must have a resolver and only these can return a Promise." Which is probably the problem. Fix is simple. I just put a resolver to property and it's working:

builder.objectType(User, {
    name: 'User',
    fields: (t) => ({
        name: t.string({ resolve: (user) => user.name }),
    }),
})

I was just wondering if there could be some settings for the builder, that could enforce that exposeString would required for property to be type of string and not promise. It could be usefull for JIT users and it would make usage with JIT more type safe.

hayes / pothos

Combination of "expose" and GraphQL JIT can cause a resolve failure #1098