fix(#4101): Increase precision for correction value transformation migration #4102
+19
−1
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
github-actions
bot
added
java
dominikriemer
approved these changes
Jan 16, 2026
tenthe
deleted the
4101-precision-loss-in-correctionvaluetransformationruledescription-migration
branch
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.
Purpose
This PR addresses an issue where the migration of
CorrectionValueTransformationRuleDescriptioncaused precision loss for small positive values. TheDecimalFormatpattern previously used a limited number of decimal places, causing values like0.00001to be rounded to0.Changes
Updated the
DecimalFormatpattern from0.###to0.########################to ensure high-precision decimals are preserved during the transformation.Remarks
PR introduces (a) breaking change(s): no
PR introduces (a) deprecation(s): no