Sorting annotation to avoid executing booleanString before trim #544
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
In the test com.univocity.parsers.common.processor.MultiBeanListProcessorTest.testAnnotatedBeanProcessor, pending used both trim and booleanString. Since getDeclaredAnnotations doesn't ensure order, it may happen booleanString is executed first and then trim. This will cause error that calling trim on boolean type. fix: typo
|
Please see #534 |
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.
Issue:
When I run the test com.univocity.parsers.common.processor.MultiBeanListProcessorTest.testAnnotatedBeanProcessor, I met the error:
Reason:
Class TestBean has two attributes "pending" and "other". The attribute used both trim and booleanString. Since getDeclaredAnnotations doesn't ensure order, it may happen BooleanString is executed first and then trim is executed. This will cause errors that call trim on Boolean type.
Changes:
In the AnnotationHelp, add logic to sort BooleanString at the end of "found" array.