Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

discussion: feature request for new version #39

Open
g00fy- opened this issue May 14, 2014 · 0 comments
Open

discussion: feature request for new version #39

g00fy- opened this issue May 14, 2014 · 0 comments

Comments

@g00fy-
Copy link
Owner

g00fy- commented May 14, 2014

I want to rewrite the whole thing as there has been some bad design decisions made in the past. What I am planning to do:

  1. Still have separate date-picker date-range input[type=date] directives
  2. Handle positioning differently (position absolute & observe window as using current implementation breaks on some pages.
  3. Change syntax of attributes/settings from max-view to something similar to ng-model-options="options"
  4. Remove the template option as this creates some overhead and makes dealing with ngModelController harder. If you still want to use custom templates then you could do:
angular.module('module',[]). directve('myCustomDatePickerDirective', function(datePickerDirective){
   return angular.extend({},datePickerDirective[0],{templateUrl:'your template'});
});
  1. Integrate with ngModelOptions (use update and debounce)
  2. Don't require jQuery
  3. Provide customizable parser that would try match format
  4. Still thinking on this - support date as string (just like <input type="datetime-local"> does)
  5. rename dist/index.js to angular-datepicker.js etc.

Please feel free to add any requests, usecases or suggestions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant