fix(ui5-step-input): prevent false validation error with valuePrecision#12778
Merged
Conversation
Collaborator
|
🧹 Preview deployment cleaned up: https://pr-12778--ui5-webcomponents.netlify.app |
NHristov-sap
approved these changes
Dec 8, 2025
tsanislavgatev
approved these changes
Dec 10, 2025
Collaborator
|
🎉 This PR is included in version v2.18.0-rc.0 🎉 The release is available on v2.18.0-rc.0 Your semantic-release bot 📦🚀 |
Collaborator
|
🎉 This PR is included in version v2.18.0 🎉 The release is available on v2.18.0 Your semantic-release bot 📦🚀 |
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
4 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.
Previously when users entered whole numbers or numbers with fewer decimals than required by
valuePrecision, the component incorrectly showed "Invalid Entry" error even though the value was automatically formatted correctly.Now integer values will always be formatted with the correct precision via
toFixed(), making them valid regardless of how they were entered (e.g., "5" or "5.0" with valuePrecision=2 both become "5.00").Fixes: #12677