[Question] Any update on #721 (automatic GraphQL type names)?

[000Janela000]

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

Not a bug report itself — just asking for an update.

Issue #721 ("Support for automatic GraphQL type names") has been open since 2021 without activity. This feature is important because manually naming every class/type adds boilerplate and can cause naming conflicts.

#721

Could you clarify the current status? Is it still planned or should we not expect it to be implemented?

Minimum reproduction code

N/A – this is a question about roadmap/planning regarding #721.

Steps to reproduce

N/A

Expected behavior

Looking for clarification: Either confirmation that the feature is still being considered or an explanation why it was deprioritized.

Package version

@nestjs/graphql: 13.x

Graphql version

graphql: 16.x

NestJS version

@nestjs/core: 11.x

Node.js version

14.17.6

In which operating systems have you tested?

• macOS
• Windows
• Linux

Other

No response

[kamilmysliwiec]

It is still being considered, but since it's never been a priority, it's basically been on hold forever