How to add a deprecationReason to a GraphQL field?
See original GitHub issueThe intended generator output is like (copied from https://docs.nestjs.com/graphql/resolvers):
@Field({ description: `Book title`, deprecationReason: 'Not useful in v2 schema' })
title: string;
Thanks!
Issue Analytics
- State:
- Created a year ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Field deprecation | Lift-off V: Production & the Schema Registry
A common situation for an evolving graph is to deprecate an existing schema field in favor of a new field. Let's see how...
Read more >Deprecation - GraphQL - Dgraph
The @deprecated directive allows you to tag the schema definition of a field or enum value as deprecated with an optional reason. When...
Read more >How to deprecate fields in GraphQL | by Kevin Simper - Medium
You can very easily deprecate a field and if you are using GraphiQL it ... When you add a deprecationReason it will automatically...
Read more >Deprecation of input fields · Issue #197 · graphql ... - GitHub
One possible workaround is to create a new field with different input, ... was just given isDeprecated and deprecationReason fields, ...
Read more >Versioning fields in GraphQL - LogRocket Blog
Whenever the change is non-breaking, as when adding a new type or field, ... isDeprecated and deprecationReason on the Field and Enum types:...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
🎉 This issue has been resolved in version 15.3.0 🎉
The release is available on:
Your semantic-release bot 📦🚀
https://github.com/unlight/prisma-nestjs-graphql#documentation-and-field-options