We no longer allow a user to tap the confirm button unless picker = still. #40
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.
TL/DR:
We no longer allow our user to tap the confirm button unless the picker is still.
Long version:
Up until now when the user interacted with the picker, if someone tapped on the confirm button, the state was not yet changed and thus the picked value would be old and miss-leading.
The DatePickerIOS does not update on the fly, and before it even manages to dispatch an update, our component is unmounted and thus the state is lost.
We no longer allow our user to tap the confirm button unless the picker is still.
They can always tap the cancel button anyway.