Fix #300: Properly reset a date widget value. #303
Merged
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
n1k0
force-pushed
the
300-fix-date-widget-reset-value
branch
from
557af37 to
c9059be
Compare
|
f+ |
|
looks good to me |
n1k0
added a commit
that referenced
this pull request
Aug 16, 2016
* Remove obsolete mention of the custom widget placeholder prop. * Fix HiddenWidget error when value is undefined (#277) * Fix SchemaField to support customized DescriptionField (#292) * Ensure arrays of numbers are properly propagated to formData (#298) * Fix #300: Properly reset a date widget value. (#303)
|
Released in v0.38.1. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This fixes #300. Deployed to gh-pages. I'd love feedback from @mplis-jetsetter and/or @vinhlh.