Reformat minDate/maxDate when dateFormat changes #131
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.
The minDate/maxDate properties are assumed to be in the same date
format as the dateFormat of the datepicker. If the datepicker is
later updated to use a new dateFormat, minDate/maxDate remain
in the old format and are not used properly by the datepicker.
With this change, when a new dateFormat is specified, minDate/maxDate
are reformatted with the new date format. This allows the datepicker
to parse those dates correctly and properly restrict the range of the
datepicker.