Verifies BigDecimal support does not have a regression#532
Merged
stleary merged 2 commits intostleary:masterfrom Jun 25, 2020
Merged
Verifies BigDecimal support does not have a regression#532stleary merged 2 commits intostleary:masterfrom
stleary merged 2 commits intostleary:masterfrom
Conversation
Add test result to confirm that stleary#531 is working in latest version.
johnjaylward
changed the title
johnjaylward
force-pushed
the
CheckBigDecimalSupport
branch
from
4542546 to
f9908a6
Compare
Owner
|
What problem does this code solve? Risks Changes to the API? Will this require a new release? Should the documentation be updated? Does it break the unit tests? Was any code refactored in this commit? Review status |
This was referenced Mar 10, 2021
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
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.
Fixes #531
Add test result to confirm that #531 is working in latest version. No code changes needed.
A new release should be scheduled so the fix can be used by people using the MAVEN artifacts.