Prevent TypeError in validateDigits when attribute value is an array #57471
+3
−2
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 pull request fixes an issue where the validateDigits method throws a TypeError when the validated attribute value is an array instead of a string.
Previously:
would throw:
Now, the method ensures that the value is a string before running the validation, preventing framework-level exceptions and keeping behavior consistent with other validation rules.
Example case:
If the request accidentally sends
code[]
, Laravel will now gracefully handle the invalid type instead of throwing an error.Impact:
This change improves robustness of the validation system by preventing a framework exception and instead treating the case as a simple validation failure.