fix: Prevent ember-pikaday from automatically updating values to within a min/max date bounds #593
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.
If merged, ember-pikaday will no longer enforce a min/max date restriction.
Original issue: #581
Ember-pikaday was running code in the modifier that would update the value to the min/max date if that value was outside of the min/max date bounds. This code was causing issues as it would update the value in the same loop that the value was read. Creating exceptions.
The readme used to have this text, we are getting rid of this:
minDate
ormaxDate
restriction