-
Notifications
You must be signed in to change notification settings - Fork 1.2k
SchemaGeneratorPostProcessing should be deprecated #2999
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.
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
Conversation
| * after the schema is built | ||
| */ | ||
| @Deprecated | ||
| @DeprecatedAt(value = "2012-10-29") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
| */ | ||
| @PublicSpi | ||
| @Deprecated | ||
| @DeprecatedAt(value = "2012-10-29") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: should be @DeprecatedAt("2022-10-29")
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
| */ | ||
| @PublicSpi | ||
| @Deprecated | ||
| @DeprecatedAt(value = "2012-10-29") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| @DeprecatedAt(value = "2012-10-29") | |
| @DeprecatedAt(value = "2022-10-29") |
SchemaGeneratorPostProcessing was a previous mechanism that
graphql.schema.SchemaTransformeris better suited toWe should not have two mechanisms for the same thing
I propose we deprecated it and remove at a later date