Input object can't have nested input object field

[ashleyxue529]

Setup

I have AInput that contains an inner BInput field that I want to setup like this:

@gqlInputObjectType()
export class AInput {
  @gqlField({
    class: "AInput",
    type: "BInput",
  })
  bInput: BInput;

  constructor(bInput: BInput) {
       this.bInput = bInput;
  }
}

@gqlInputObjectType()
export class BInput {
  @gqlField({
    class: "BInput",
    type: GraphQLID,
  })
  id: string;

  @gqlField({
    class: "BInput",
    type: GraphQLInt,
  })
  quantity: number;

  constructor(id: string, quantity: number) {
    this.id = id;
    this.quantity = quantity;
  }
}

But I can't regen the code due to this error:

field bInput references BInput which isn't a graphql object

I tried setting up BInput using @gqlObjectType instead, which seems to successfully regen, but the graphql type is incorrect as it needs to be an Input type not just a generic type, so the server just errors out.

Question

Should there be a separate @gqlInputField we can use? Or is there a setup I'm missing? Thanks!

[ashleyxue529]

Nvmind figured out part of it, need to use custom type instead of this setup

[lolopinto]

What was the custom type solution you used? Looking at the example, it feels like it should work so may still be worth fixing eventually.

…

On Tue, Feb 20, 2024 at 22:17 Ashley Xue ***@***.***> wrote: Nvmind figured out part of it, need to use custom type instead of this setup — Reply to this email directly, view it on GitHub <#1754 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACS2VN2PMBNNFFABLQTX2Y3YUWGOZAVCNFSM6AAAAABDM5QCUSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJVHE3DOMBRGQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[ashleyxue529]

@lolopinto there were two setups that compiled with custom types, but only one actually generated the schema.gql file correctly

1. [worked] Using structFields + inputType, not actually sure if I'm using it correctly but the type is correct in the gql schema

 type: {
      type: "TestInput",
      importPath: "i don't think this path does anything if we use structFields, but it is still required to be used for custom type",

      structFields: {
        id: UUIDType({ nullable: true }),
      },
      inputType: true,
 },

2. [partially worked] Just using import paths, but no type is generated in the gql schema (is this a bug?)

@gqlInputObjectType()
class TestInput {
  @gqlField({
    class: "TestInput",
    type: GraphQLString,
  })
  id: string;

  constructor(id: string) {
    this.id = id;
  }
}

const GraphQLTestInput = new GraphQLInputObjectType({
  name: "TestInput",
  fields: (): GraphQLInputFieldConfigMap => ({
    id: {
      type: new GraphQLNonNull(GraphQLID),
    },
  }),
});

 type: {
      type: "GraphQLTestInput",
      importPath: "",
      tsType: "TestInput",
      tsImportPath: ""
 },

I think you also see this in the example you provided here, there's no ContactLabel2 type in the schema:

• https://github.com/lolopinto/ent/blob/main/examples/simple/src/graphql/mutations/import_contact.ts#L36-L44
• https://github.com/lolopinto/ent/blob/main/examples/simple/src/graphql/generated/schema.gql

Looking at the example, it feels like it should work so may still be worth fixing eventually.

Do we possibly need something like @gqlInputField to differentiate? Yeah, ideally we could set it up like the example above instead of using custom types, it feels more intuitive to just nest Input Types

[ashleyxue529]

Gonna reopen this as I think this is still worth updating as I ran into this again. Though please let me know if I'm just doing it wrong. Basically just trying to do:

@gqlInputObjectType()
export class CreateObjectInput {
  @gqlField({
    class: "CreateObjectInput",
    type: "[CreateObjectBInput]", <- this type is generated through the schema graphql action codegen
  })
  objectBInputs: string;
}

which gives Error: field objectBInputs references CreateObjectBInput which isn't a graphql object

[lolopinto]

presumably, you're still using v0.1.x and not on the v0.2.0-alpha, right?

fixed in main but will need to backport a few things over for v0.1.x