This repository was archived by the owner on Sep 5, 2024. It is now read-only.
fix(datepicker): support ng-model-options timezone w/ Moment #11951
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.
PR Checklist
Please check that your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
1.1.23
broke the MomentJS demos of the datepicker1.1.23
, PR feat(calendar): support specifying timezone in ng-model-options #11906 implemented support inmd-calendar
forng-model-options
, but it isn't hooked up to themd-datepicker
to pass in itsng-model-options
to the associated `md-calendar (datepicker: md-calendar panel should respect ng-model-options #10598).Issue Number:
Fixes #11945. Fixes #10598.
What is the new behavior?
ng-model-options
timezone w/ Momentng-model-options
timezone supportng-model-options
on to its calendarDoes this PR introduce a breaking change?
Other information
This just merges the change in the
1.1.x
branch tomaster
.