[12.x] Allows for strict numeric validation #56328
Merged
+30
−3
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.
Changes
validateNumeric
inValidatesAttributes
trait to accept astrict
parameter.validateNumeric
in other validation methods to provide the new parameter.Why
Same purpose as #56313. This would allow for blocking strings being used in JSON requests for numbers e.g. allow
1
but not'1'
. This is useful for APIs where allowing strings might not be what the end user wants compared to web forms that are more flexible when it comes to strings.Notes
I've kept this to just numeric as that will work with both floats and integers rather than applying this parameter to the wide range of number based options.