-
Notifications
You must be signed in to change notification settings - Fork 23
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
ui: date-range-picker - add support for ControlValueAccessor, MatFormFieldControl and Validator #1197
Comments
carlo-nomes
added a commit
to carlo-nomes/stark
that referenced
this issue
Apr 17, 2019
… component - provide functionality for displaying errors - added example - added test ISSUES CLOSED: NationalBankBelgium#1197
carlo-nomes
added a commit
to carlo-nomes/stark
that referenced
this issue
Apr 17, 2019
… component - provide functionality for displaying errors - added example - added test ISSUES CLOSED: NationalBankBelgium#1197
3 tasks
carlo-nomes
added a commit
to carlo-nomes/stark
that referenced
this issue
Apr 17, 2019
… component - provide functionality for displaying errors - added example - added test ISSUES CLOSED: NationalBankBelgium#1197
carlo-nomes
added a commit
to carlo-nomes/stark
that referenced
this issue
Apr 17, 2019
… component - provide functionality for displaying errors - added example - added test ISSUES CLOSED: NationalBankBelgium#1197
carlo-nomes
added a commit
to carlo-nomes/stark
that referenced
this issue
Apr 17, 2019
… component - provide functionality for displaying errors - update stark-date-pickers with two way binding - added example - added/updated test ISSUES CLOSED: NationalBankBelgium#1197
carlo-nomes
added a commit
to carlo-nomes/stark
that referenced
this issue
Apr 23, 2019
… component - provide functionality for displaying errors - update stark-date-pickers with two way binding - added example - added/updated test ISSUES CLOSED: NationalBankBelgium#1197
carlo-nomes
added a commit
to carlo-nomes/stark
that referenced
this issue
Apr 23, 2019
… component - provide functionality for displaying errors - update stark-date-pickers with two way binding - added example - added/updated test ISSUES CLOSED: NationalBankBelgium#1197
carlo-nomes
added a commit
to carlo-nomes/stark
that referenced
this issue
Apr 24, 2019
… component - provide functionality for displaying errors - update stark-date-pickers with two way binding - added example - added/updated test ISSUES CLOSED: NationalBankBelgium#1197
carlo-nomes
added a commit
to carlo-nomes/stark
that referenced
this issue
Apr 24, 2019
… component - provide functionality for displaying errors - update stark-date-pickers with two way binding - added example - added/updated test ISSUES CLOSED: NationalBankBelgium#1197
carlo-nomes
added a commit
to carlo-nomes/stark
that referenced
this issue
Apr 24, 2019
… component - provide functionality for displaying errors - update stark-date-pickers with two way binding - added example - added/updated test ISSUES CLOSED: NationalBankBelgium#1197
carlo-nomes
added a commit
to carlo-nomes/stark
that referenced
this issue
Apr 24, 2019
… component - provide functionality for displaying errors - update stark-date-pickers with two way binding - added example - added/updated test ISSUES CLOSED: NationalBankBelgium#1197
carlo-nomes
added a commit
to carlo-nomes/stark
that referenced
this issue
Apr 25, 2019
… component - provide functionality for displaying errors - update stark-date-pickers with two way binding - added example - added/updated test ISSUES CLOSED: NationalBankBelgium#1197
carlo-nomes
added a commit
to carlo-nomes/stark
that referenced
this issue
Apr 25, 2019
… component - provide functionality for displaying errors - update stark-date-pickers with two way binding - added example - added/updated test ISSUES CLOSED: NationalBankBelgium#1197
carlo-nomes
added a commit
to carlo-nomes/stark
that referenced
this issue
Apr 25, 2019
… component - provide functionality for displaying errors - update stark-date-pickers with two way binding - added example - added/updated test ISSUES CLOSED: NationalBankBelgium#1197
carlo-nomes
added a commit
to carlo-nomes/stark
that referenced
this issue
Apr 25, 2019
… component - provide functionality for displaying errors - update stark-date-pickers with two way binding - added example - added/updated test ISSUES CLOSED: NationalBankBelgium#1197
carlo-nomes
added a commit
to carlo-nomes/stark
that referenced
this issue
Apr 26, 2019
… component - provide functionality for displaying errors - update stark-date-pickers with two way binding - added example - added/updated test ISSUES CLOSED: NationalBankBelgium#1197
carlo-nomes
added a commit
to carlo-nomes/stark
that referenced
this issue
Apr 30, 2019
… component - provide functionality for displaying errors - update stark-date-pickers with two way binding - added example - added/updated test ISSUES CLOSED: NationalBankBelgium#1197
carlo-nomes
added a commit
to carlo-nomes/stark
that referenced
this issue
Apr 30, 2019
… component - provide functionality for displaying errors - update stark-date-pickers with two way binding - added example - added/updated test ISSUES CLOSED: NationalBankBelgium#1197
carlo-nomes
added a commit
to carlo-nomes/stark
that referenced
this issue
Apr 30, 2019
… component - provide functionality for displaying errors - update stark-date-pickers with two way binding - added example - added/updated test ISSUES CLOSED: NationalBankBelgium#1197
christophercr
pushed a commit
to carlo-nomes/stark
that referenced
this issue
May 3, 2019
… component - provide functionality for displaying errors - update stark-date-pickers with two way binding - added example - added/updated test ISSUES CLOSED: NationalBankBelgium#1197 BREAKING CHANGES: `stark-date-range-picker` is now implemented as a ControlValueAccessor to better integrate with Angular Forms: - new `rangeFormGroup` input to provide the start and end date form controls. You can handle validations and error messages via those form controls. - new `required` input to mark the control as required and display the required asterisk '*' in the start/end date pickers (same as with the `stark-date-picker`). - the `isDisabled` input has been renamed to `disabled`. If you use the new `rangeFormGroup` input to provide your start/end date form controls, then you should disable/enable those form controls directly yourself instead of using the `disabled` input.
christophercr
pushed a commit
to carlo-nomes/stark
that referenced
this issue
May 14, 2019
… component - provide functionality for displaying errors - update stark-date-pickers with two way binding - added example - added/updated test ISSUES CLOSED: NationalBankBelgium#1197 BREAKING CHANGES: `stark-date-range-picker` is now implemented as a ControlValueAccessor to better integrate with Angular Forms: - new `rangeFormGroup` input to provide the start and end date form controls. You can handle validations and error messages via those form controls. - new `required` input to mark the control as required and display the required asterisk '*' in the start/end date pickers (same as with the `stark-date-picker`). - the `isDisabled` input has been renamed to `disabled`. If you use the new `rangeFormGroup` input to provide your start/end date form controls, then you should disable/enable those form controls directly yourself instead of using the `disabled` input.
christophercr
pushed a commit
to carlo-nomes/stark
that referenced
this issue
May 14, 2019
… component - provide functionality for displaying errors - update stark-date-pickers with two way binding - added example - added/updated test ISSUES CLOSED: NationalBankBelgium#1197 BREAKING CHANGES: `stark-date-range-picker` is now implemented as a ControlValueAccessor to better integrate with Angular Forms: - new `rangeFormGroup` input to provide the start and end date form controls. You can handle validations and error messages via those form controls. - new `required` input to mark the control as required and display the required asterisk '*' in the start/end date pickers (same as with the `stark-date-picker`). - the `isDisabled` input has been renamed to `disabled`. If you use the new `rangeFormGroup` input to provide your start/end date form controls, then you should disable/enable those form controls directly yourself instead of using the `disabled` input.
christophercr
pushed a commit
to carlo-nomes/stark
that referenced
this issue
May 14, 2019
… component - provide functionality for displaying errors - update stark-date-pickers with two way binding - added example - added/updated test ISSUES CLOSED: NationalBankBelgium#1197 BREAKING CHANGES: `stark-date-range-picker` is now implemented as a ControlValueAccessor to better integrate with Angular Forms: - new `rangeFormGroup` input to provide the start and end date form controls. You can handle validations and error messages via those form controls. - new `required` input to mark the control as required and display the required asterisk '*' in the start/end date pickers (same as with the `stark-date-picker`). - the `isDisabled` input has been renamed to `disabled`. If you use the new `rangeFormGroup` input to provide your start/end date form controls, then you should disable/enable those form controls directly yourself instead of using the `disabled` input.
christophercr
pushed a commit
to carlo-nomes/stark
that referenced
this issue
May 20, 2019
… component - provide functionality for displaying errors - update stark-date-pickers with two way binding - added example - added/updated test ISSUES CLOSED: NationalBankBelgium#1197 BREAKING CHANGES: `stark-date-range-picker` is now implemented as a ControlValueAccessor to better integrate with Angular Forms: - new `rangeFormGroup` input to provide the start and end date form controls. You can handle validations and error messages via those form controls. - new `required` input to mark the control as required and display the required asterisk '*' in the start/end date pickers (same as with the `stark-date-picker`). - the `isDisabled` input has been renamed to `disabled`. If you use the new `rangeFormGroup` input to provide your start/end date form controls, then you should disable/enable those form controls directly yourself instead of using the `disabled` input.
christophercr
pushed a commit
to carlo-nomes/stark
that referenced
this issue
May 27, 2019
… component - provide functionality for displaying errors - update stark-date-pickers with two way binding - added example - added/updated test ISSUES CLOSED: NationalBankBelgium#1197 BREAKING CHANGES: `stark-date-range-picker` is now implemented as a ControlValueAccessor to better integrate with Angular Forms: - new `rangeFormGroup` input to provide the start and end date form controls. You can handle validations and error messages via those form controls. - new `required` input to mark the control as required and display the required asterisk '*' in the start/end date pickers (same as with the `stark-date-picker`). - the `isDisabled` input has been renamed to `disabled`. If you use the new `rangeFormGroup` input to provide your start/end date form controls, then you should disable/enable those form controls directly yourself instead of using the `disabled` input.
christophercr
pushed a commit
to carlo-nomes/stark
that referenced
this issue
May 27, 2019
… component - provide functionality for displaying errors - update stark-date-pickers with two way binding - added example - added/updated test ISSUES CLOSED: NationalBankBelgium#1197 BREAKING CHANGES: `stark-date-range-picker` is now implemented as a ControlValueAccessor to better integrate with Angular Forms: - new `rangeFormGroup` input to provide the start and end date form controls. You can handle validations and error messages via those form controls. - new `required` input to mark the control as required and display the required asterisk '*' in the start/end date pickers (same as with the `stark-date-picker`). - the `isDisabled` input has been renamed to `disabled`. If you use the new `rangeFormGroup` input to provide your start/end date form controls, then you should disable/enable those form controls directly yourself instead of using the `disabled` input.
christophercr
pushed a commit
to carlo-nomes/stark
that referenced
this issue
May 27, 2019
… component - provide functionality for displaying errors - update stark-date-pickers with two way binding - added example - added/updated test ISSUES CLOSED: NationalBankBelgium#1197 BREAKING CHANGES: `stark-date-range-picker` is now implemented as a ControlValueAccessor to better integrate with Angular Forms: - new `rangeFormGroup` input to provide the start and end date form controls. You can handle validations and error messages via those form controls. - new `required` input to mark the control as required and display the required asterisk '*' in the start/end date pickers (same as with the `stark-date-picker`). - the `isDisabled` input has been renamed to `disabled`. If you use the new `rangeFormGroup` input to provide your start/end date form controls, then you should disable/enable those form controls directly yourself instead of using the `disabled` input.
christophercr
pushed a commit
to carlo-nomes/stark
that referenced
this issue
May 27, 2019
… component - provide functionality for displaying errors - update stark-date-pickers with two way binding - added example - added/updated test ISSUES CLOSED: NationalBankBelgium#1197 BREAKING CHANGES: `stark-date-range-picker` is now implemented as a ControlValueAccessor to better integrate with Angular Forms: - new `rangeFormGroup` input to provide the start and end date form controls. You can handle validations and error messages via those form controls. - new `required` input to mark the control as required and display the required asterisk '*' in the start/end date pickers (same as with the `stark-date-picker`). - the `isDisabled` input has been renamed to `disabled`. If you use the new `rangeFormGroup` input to provide your start/end date form controls, then you should disable/enable those form controls directly yourself instead of using the `disabled` input.
christophercr
pushed a commit
to carlo-nomes/stark
that referenced
this issue
May 28, 2019
… component - provide functionality for displaying errors - update stark-date-pickers with two way binding - added example - added/updated test ISSUES CLOSED: NationalBankBelgium#1197 BREAKING CHANGES: `stark-date-range-picker` is now implemented as a ControlValueAccessor to better integrate with Angular Forms: - new `rangeFormGroup` input to provide the start and end date form controls. You can handle validations and error messages via those form controls. - new `required` input to mark the control as required and display the required asterisk '*' in the start/end date pickers (same as with the `stark-date-picker`). - the `isDisabled` input has been renamed to `disabled`. If you use the new `rangeFormGroup` input to provide your start/end date form controls, then you should disable/enable those form controls directly yourself instead of using the `disabled` input.
christophercr
pushed a commit
to carlo-nomes/stark
that referenced
this issue
May 28, 2019
… component - provide functionality for displaying errors - update stark-date-pickers with two way binding - added example - added/updated test ISSUES CLOSED: NationalBankBelgium#1197 BREAKING CHANGES: `stark-date-range-picker` is now implemented as a ControlValueAccessor to better integrate with Angular Forms: - new `rangeFormGroup` input to provide the start and end date form controls. You can handle validations and error messages via those form controls. - new `required` input to mark the control as required and display the required asterisk '*' in the start/end date pickers (same as with the `stark-date-picker`). - the `isDisabled` input has been renamed to `disabled`. If you use the new `rangeFormGroup` input to provide your start/end date form controls, then you should disable/enable those form controls directly yourself instead of using the `disabled` input.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm submitting a...
Current behavior
The date-range-picker component is restrictive to use and not intuitive enough comparing to all
@angular/material
components.The developer cannot :
[(ngModel)]
[formControl]
(we can use[dropdownFormControl]
Expected behavior
The date-range-picker component should be usable like the
@angular/material
components.We did already this for the date-picker component: #1178
What is the motivation / use case for changing the behavior?
Standardize our components to what is already proposed by Angular Material.
The text was updated successfully, but these errors were encountered: