Support the new endpoint tags API #118
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
Generate changelog in
|
sfackler
force-pushed
the
tags
branch
2 times, most recently
from
1362ff4 to
bc25f2d
Compare
dtobin
approved these changes
Oct 30, 2020
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.
Before this PR
Service argument safety was indicated by a marker corresponding to a Java
Safeannotation.After this PR
==COMMIT_MSG==
Server endpoint arguments with the
safetag will be marked as safe.==COMMIT_MSG==
We now support the newly-added
tagsAPI (palantir/conjure#702) which bypasses the Java annotation bit in favor of a more language-agnostic approach. The old marker annotation is still supported to preserve back compat.