Date validation on input was broken #559
Closed
Conversation
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
…turns false, unlike isNaN('Invalid Date')
|
Fixed in the meantime, will close this pull request. |
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.
Valid date validation on input is broken.
This is because Number.isNaN('Invalid Date') returns false (Number.isNaN returns true only if the parameter is NaN), unlike isNaN('Invalid Date').
See this for more information:
https://stackoverflow.com/questions/1353684/detecting-an-invalid-date-date-instance-in-javascript
Currently, if you dropdown a daterange, select a date and then manually modify it to an invalid date (say, deleting a digit from the month), the entire dropdown calendar will show invalid date or Inv...
This pull request fixes this.