Option To Display Numbers With Less Precision #4640
Merged
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.
Fix #4626. Previous changes had increased the precision of floating point numbers when cast to string, making for greater accuracy after save and load operations, without affecting the values displayed by Excel. Although the results of the cast are now more accurate computationally, they can appear unexpected to humans. A new boolean parameter
lessFloatPrecision(defaulting to false) is added toStringHelper::convertToString, toNumberFormat::toFormattedStringandNumberFormat\Formatter::toFormattedString, and to the entireWorksheet::toArrayfamily of functions. When the new parameter is set to true, the result can be less surprising to humans. It should not, however, be used in subsequent computations.In the case of the NumberFormat functions, the new parameter will be considered only when the NumberFormat for the cell in question is
Generalor equivalent. Setting an actual numeric format for the cell is probably a better solution than using the new parameter.This is:
Checklist: