How to generate types in thier own files?

[IvanKalinin]

Is it possible to generate each type, enum in its own file, like in openapi-typescript-codegen instead of a single file?

[mrlubos]

Hi @IvanKalinin, not at the moment. What would be the use case?

[IvanKalinin]

That would allow me to migrate from openapi-typescript-codegen seamlessly. And overall I prefer to import like import { UserResponse } from '@mymonorepo/models/UserResponse'. Feels cleaner, and easier to maintain (e.g. on generating I immediately see what types were updated by their filenames in git status.

[mrlubos]

If I remember correctly, those files contain only the exported type, correct? So both import { UserResponse } from '@mymonorepo/models/UserResponse' and import { UserResponse } from '@mymonorepo/types.gen' convey the same meaning. Even if we supported the former and assuming exports follow the same naming pattern, the generated folder/file isn't called models anymore.

I'm also curious about the second part of your comment.

on generating I immediately see what types were updated by their filenames in git status

Are you able to describe your workflow? Also, how big is your team and how often do you need to see what changed?

[IvanKalinin]

Depends on the project. Some projects I work on consistently develop new features, deprecate some stuff, and so on. I regenerate types at least once in 3-4 weeks.
Some fields here, some there, you know. Actively developing product.