-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
Support the full FormControl API #38
Comments
Add the types of the emissions * Type encapsulating the Angular Form options:
* `emitEvent` - do we emit event;
* `onlySelf` - do we bubble up to parent
* `emitModelToViewChange` - When true or not supplied (the default), each change triggers an onChange event to update the view.
* `emitViewToModelChange` - When true or not supplied (the default), each change triggers an ngModelChange event to update the model.
*/
export interface FormEventOptions {
emitEvent?: boolean;
onlySelf?: boolean;
emitModelToViewChange?: boolean;
emitViewToModelChange?: boolean;
} |
Handing ValidatorFn[] and AsyncValidatorFn[] seems to be done by just adding these to the constructor call in the types. Or am I missing something here? So can this issue be closed with a new minor version in the near future? @gparlakov |
@Mongole666 yes - you are correct, I just saw that the In the mean time
|
@Mongole666 just released version 1.1.2 with support for that |
Support the AbstractFormControlOptions:
The text was updated successfully, but these errors were encountered: