TypeDescriptor.equals tests equality of annotations #924
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
…notation properties) Issue: SPR-13714
Contributor
|
Thanks for the pull request! I've rolled this in a slightly revised fashion, including some general rearrangments in the affected tests. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
The current implementation of TypeDescriptor.equals merely tests for the presence of annotations between the compared type descriptors, as apposed to also comparing annotation property values.
This ultimately lead to problems with the GenericConversionService cache returning the "wrong" conditional converter in my application.
I have signed and agree to the terms of the Spring Individual Contributor
License Agreement.
Issue: SPR-13714