A bug? with payload generated types vs the API response for a type

[hexed pivot]

So payload generate:types produces:

export interface Usecase {
  id: string;
  slug: string;
  title: string;
  rank: number;
  shortDescription: string;
  longDescription: string;
  orgDescriptionOverride?: boolean | null;
  orgSpecificDescriptions?: OrgSpecificDescriptions;
  category?: (string | null) | Category;
  updatedAt: string;
  createdAt: string;
}
export interface OrgSpecificDescriptions {
  organizationId?: string | null;
  orgShortDescription: string;
  orgLongDescription: string;
}

[unreal juniper]

New Community-Help Thread Created!

Help is on the way! To mark it as solved, use the /solve command. In the meantime, here are some existing threads that may help you:

Documentation:

• using-your-types
• types
• validation
• object-object-option
• adding-your-own-queries-and-mutations

[hexed pivot]

But an API response will produce:

       "orgSpecificDescriptions": {},

thus, if you try to directly use the generated types, it will complain that orgSpecificDescription is not "of type" OrgSpecificDescriptions