Handle null/undefined options for isInt and isFloat #2330
Closed
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.
What has been modified
Bug(isInt): Returns true in case an option was passed as null/undefined for that specific condition
Bug(isFloat): Returns true in case an option was passed as null/undefined for that specific condition
What has been done
Added checks for null and undefined in both functions
isInt
andisFloat
to be able to handle cases of null/undefinedOld code example:
Updated (New) code example:
Issue Referenced
#2328
Checklist