fix(number): replace Number with parseFloat for inline width parsing and remove Number #7603#8027
Merged
deleonio merged 1 commit intopublic-ui:developfrom Jul 15, 2025
Conversation
2 tasks
deleonio
approved these changes
Jul 15, 2025
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Beschreibung der Änderungen
Im Rahmen des Tickets #7603 wurden gezielt zwei Stellen im Code überarbeitet, um die Verwendung von
Number()zu vermeiden und durch geeignetere Alternativen zu ersetzen:Formularfeld – toFixed-Anwendung
Die bisherige Umwandlung
Number(field.value).toFixed(2)wurde durchfield.value.toFixed(2)ersetzt. Da zuvor bereits geprüft wird, obfield.valuevom Typnumberist, war der Einsatz vonNumber()überflüssig.CSS-Style – Breitenwert parsen
Beim Einlesen des
width-Werts aus einem CSS-String (z. B."120px") wurdeNumber(...)durchparseFloat(...)ersetzt. Dies ermöglicht eine korrekte Verarbeitung auch bei Dezimalwerten