add deprecate annotation #261
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
depends on #260 as it might affect the Go code gen result. |
EdSchouten
approved these changes
Jun 9, 2023
Merged
mostynb
approved these changes
Jun 9, 2023
bergsieker
approved these changes
Jun 9, 2023
sluongng
force-pushed
the
sluongng/deprecate-annotation
branch
from
58a69f7
to
d3ddb45
Compare
|
Rebased 🙏 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This helps signal to downstream API consumers, via code gen results,
that the fields are deprecated and their usage is discouraged.