Added event emit to setDate method #34
Open
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
…orm additional actions.
…wer and package JSON
|
How can I track this event? |
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.
We required notification when a date picker has changed the value as ng-change does not capture the value programmatically and angular watchers were not triggering.
The emit fires a "datetime-picker-changed" event with the field id and the new date value. This has been tested with multiple date pickers - passing different details to the scope - on the same page (child and parent directives have a 1:1 relationship).
Updated README.md with attr details and package.json for typo.
minified JS updated using JSCompress.