How to use inputObjectType as types?

[hyochan]

Say I have defined below.

export const MessageCreateInput = inputObjectType({
  name: 'MessageCreateInput',
  definition(t) {
    t.messageType('messageType');
    t.string('text');
    t.string('imageUrls', { list: true });
    t.string('fileUrls', { list: true });
  },
});

When I don't specify Message interface, it will throw tsc error since the input type from the argument are all any.

    interface Message {
      text?: string;
      messageType?: MessageType,
      fileUrls?: string[],
      imageUrls?: string[],
    }

    const createMessage = (
      { text, messageType, fileUrls, imageUrls } : Message,
      channelId: string,
    ) => ctx.prisma.message.create({
      data: {
        text,
        messageType,
        fileUrls: { set: fileUrls },
        imageUrls: { set: imageUrls },
        channel: { connect: { id: channelId } },
        sender: { connect: { id: userId } },
      },
    });

Is there a way to use inputObjectType as type?

[ElijahFosterbee]

If you're using Nexus, that's expected behavior. The GraphQL input definition only exists at the schema level and doesn't automatically provide TypeScript types unless you've enabled type generation and wired it up correctly. Without that, the resolver arguments are often inferred as any, which is why you need the Message interface. A common approach is to either keep a separate TypeScript interface like you're doing or use Nexus typegen so the input type can be inferred directly from MessageCreateInput. That way you get proper type safety without manually maintaining duplicate definitions. QuickWin Casino offers a large selection of slots, table games, and live casino titles, making it an appealing option for players looking for a varied https://quickwin-casino.net/ online gaming experience.