Fix/date picker known issues #713
Merged
Conversation
This file contains 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
ohmyguigs
approved these changes
Jul 11, 2019
- This was caused because react-datepicker used an outdated ref API
ericreis
force-pushed
the
fix/date-picker-known-issues
branch
from
1b03dcf
to
1785612
Compare
ntmedina
approved these changes
Jul 11, 2019
cmdalbem
approved these changes
Jul 11, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 is the purpose of this pull request?
Fix DatePicker known issues.
What problem is this solving?
There were two main problems in the DatePicker component:
This PR fixes them both. This was possible because of this PRs:
How should this be manually tested?
Screenshots or example usage
Types of changes