Fixed #17490: use numeric for purchase cost#17555
Merged
Conversation
Signed-off-by: snipe <snipe@snipe.net>
Yvejen
pushed a commit
to Yvejen/snipe-it
that referenced
this pull request
Nov 19, 2025
…-use-numeric-for-purchase-cost Fixed grokability#17490: use numeric for purchase cost
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
1 participant
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.
This forces the field type of be number so that if you accidentally add a currency symbol, it will fail validation.
I don't expect most people to use the stepper, as they're generally pretty annoying, however we have to use xx.xxx (vers xx.xx) because some currencies use three numbers after the decimal point.
Fixes #17490