Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

@InputType field can not be deprecated #2354

Closed
2 of 4 tasks
dersar00 opened this issue Aug 25, 2022 · 1 comment
Closed
2 of 4 tasks

@InputType field can not be deprecated #2354

dersar00 opened this issue Aug 25, 2022 · 1 comment
Labels
bug needs triage

Comments

@dersar00
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Current behavior

Adding a @InputType field a deprecationReason option does not apply and it is missing in the generated schema.

Minimum reproduction code

https://github.com/dersar00/nest-gql-input-type-bug

Steps to reproduce

No response

Expected behavior

The @InputType field works the same as the @ObjectType and can be deprecated.

Package version

10.0.16

Graphql version

graphql: 15.5.1
apollo-server-express: 3.3.0

NestJS version

8.2.3

Node.js version

16.13.1

In which operating systems have you tested?

  • macOS
  • Windows
  • Linux

Other

No response
@kamilmysliwiec
Copy link
Member

graphql/graphql-spec#197

@nestjs nestjs locked and limited conversation to collaborators Aug 26, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug needs triage
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dersar00 @kamilmysliwiec