Skip to content
This repository has been archived by the owner on May 29, 2019. It is now read-only.

feat(datepicker): ng-model-options: timezone #5062

Closed

Conversation

davious
Copy link
Contributor

@davious davious commented Dec 13, 2015

@davious davious force-pushed the datepicker-ng-model-options branch 3 times, most recently from a1c26a6 to ef4189c Compare December 13, 2015 16:34
@@ -100,6 +100,10 @@ The datepicker has 3 modes:
allowInvalid support. [More on ngModelOptions](https://docs.angularjs.org/api/ng/directive/ngModelOptions).


* `ng-model-options`
_(Default: {})_ -
Timezone support. [More on ngModelOptions](https://docs.angularjs.org/api/ng/directive/ngModelOptions).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be condensed with the ng-model-options block directly above, changing the allowInvalid and timezone mention to sub-bullet points.

@davious davious force-pushed the datepicker-ng-model-options branch from ef4189c to 30079ec Compare December 15, 2015 02:49
@wesleycho
Copy link
Contributor

The dateparser additions will need unit tests.

@@ -571,6 +579,8 @@ function(scope, element, attrs, $compile, $parse, $document, $rootScope, $positi
if (datepickerPopupConfig.html5Types[attrs.type]) {
dateFormat = datepickerPopupConfig.html5Types[attrs.type];
isHtml5DateInput = true;
ngModelOptions.timezoneHtml5 = ngModelOptions.timezone;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a particular reason for splitting this out?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a great question. Looking through the changes, the distinction seems superfluous. I forget why I made the distinction in the first place. Let me remove it.

@wesleycho
Copy link
Contributor

I think this is close to done, just needs those tasks/questions to be answered and this should be good to merge. This is a lot cleaner than my own attempt at it.

@wesleycho wesleycho added this to the 1.0.0 milestone Dec 15, 2015
@davious davious force-pushed the datepicker-ng-model-options branch 2 times, most recently from 8348d8e to 469477d Compare December 16, 2015 06:04
@davious davious force-pushed the datepicker-ng-model-options branch from 469477d to 32071bb Compare December 16, 2015 06:06
@wesleycho wesleycho closed this in 09098f8 Dec 16, 2015
@davious davious deleted the datepicker-ng-model-options branch December 28, 2015 00:00
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants