fix for #16: chore(datepicker): support null value #445
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
|
hey, looks good, let me check |
JohanSmolders
force-pushed
the
development
branch
from
6afc2d6
to
47b61df
Compare
added 3 commits
April 26, 2016 15:38
Introduced support for null as default value: - In the ngOnInit method of the datepicker-inner class the update should only emit when selectedDate is changed. - Extra check in compare function - activeDate() shouldn't return today when not set
…to select a date in pop-up. It doesn't reflect selected-date.
…to select a date in pop-up. It doesn't reflect selected-date.
JohanSmolders
force-pushed
the
development
branch
from
47b61df
to
997aa38
Compare
|
Sorry about that, fixed it. |
|
no worries, always rebase on default branch (here it is dev) :) |
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.
Introduced support for null as default value: