add deprecation warnings #1128
Merged
add deprecation warnings #1128
Conversation
This file contains hidden or 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
john-h-kastner-aws
approved these changes
Aug 8, 2024
shaobo-he-aws
approved these changes
Aug 8, 2024
Co-authored-by: Craig Disselkoen <[email protected]>
shaobo-he-aws
approved these changes
Aug 8, 2024
cdisselkoen
approved these changes
Aug 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Description of changes
Add deprecation warnings to 3.3.x to support the API changes in the following PRs.
ParseErrors::errors_as_strings(fix #543) #882ParseError#908DisplayforEntityIdin favor of explicit.escaped()and.as_ref()#921This list of PRs is based on manual inspection of the 4.0 changelog to look for APIs that were removed or renamed. Let me know if you think I missed anything.