How to get Types and Enums ? (Angular)

[rudyhadoux]

Hi,

I've just started Gen 2.

Why don't you generate a TypeScript file with all the types and enums, so that we can import them into the front-end code ?
It would be great if Amplify could automatically generate a file of types and enums in Amplify folder, directly usable for the front-end.

Typing helps to avoid many errors.

[pranavosu]

Hi @rudyhadoux, welcome to Gen 2. This already works, just differently from Gen 1. Gen 2 skips the codegen step entirely and derives types straight from your schema via TypeScript inference. No generated files to commit or keep in sync.

In your amplify/data/resource.ts:

import { a, defineData, type ClientSchema } from '@aws-amplify/backend';

const schema = a.schema({
  Post: a.model({
    title: a.string().required(),
    status: a.enum(['draft', 'published', 'archived']),
  }).authorization(allow => [allow.publicApiKey()]),
});

export type Schema = ClientSchema<typeof schema>;

Then in your Angular code:

import type { Schema } from '../../amplify/data/resource';

// Full model type (what the client returns)
type Post = Schema['Post']['type'];

// Shape for create / update inputs
type NewPost = Schema['Post']['createType'];

// Enum values as a string union
type PostStatus = Post['status']; // 'draft' | 'published' | 'archived' | null

Pass Schema into generateClient<Schema>() and every query, mutation, and subscription is fully typed, including nested relationships and enum fields.

Docs with more examples:

• Set up data
• Query data (shows the Schema["Post"]["type"] patterns)

The swap from Angular to React in those URLs is cosmetic; the TypeScript patterns are identical.

If there's a specific case where this inference-based approach isn't covering your use case (for example, wanting enum values as runtime constants, not just types), let us know and we can dig into that.

[rudyhadoux]

Yes but we have to add this

type Post = Schema['Post']['type'];
type NewPost = Schema['Post']['createType'];
type PostStatus = Post['status'];

If all the types and enums were directly in one file, it would be easier and faster to use...
If all the types and enums are already in a file in the Amplify directory, VS Code will import them directly.

With Gen 1, all types were in graphql directory and API.ts.

[rudyhadoux]

For enums, the format is :

export enum StatutEnterprise {
ACTIVE = 'ACTIVE',
INACTIVE = 'INACTIVE',
}

[soberm]

Hi @rudyhadoux,
thanks for the follow-up. I see the pain points. We will discuss this with the team and provide any updates here.