Bugfix/16181 number field amends #16192
Merged
+7
−8
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.
Description
In v4, if you type 5.6 into a number field which has decimals set to zero, the value stored in the DB is 5; the value displayed in the control panel and on the front end is also 5 (that’s because the decimals setting affected the type of column the data was saved to).
In v5, it’s
Since we no longer rely on column types, normalisation should take care of ensuring the field’s decimals setting is respected.
Related issues
#16181