We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The IxSelectComponent on Angular should work natively with either with Template Driven or Reactive Forms.
As an example for Template Driven form:
<ix-select [(ngModel)]="value" name="select-control"> <ix-select-option value="1" label="Option 1"/> <ix-select-option value="2" label="Option 2"/> </ix-select>
and Reactive form:
<ix-select [formControl]="form"> <ix-select-option value="1" label="Option 1"/> <ix-select-option value="2" label="Option 2"/> </ix-select>
For this an implementation of a directive using the ControlValueAccessor interface should be created. Happy to create PR for this.
The text was updated successfully, but these errors were encountered:
Sounds good. But keep in mind we are using the stencil-out-targets, this provides the posibility to generate valueAccessors out of the webcomponents https://stenciljs.com/docs/angular#valueaccessorconfigs
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Suggestion / feature request
The IxSelectComponent on Angular should work natively with either with Template Driven or Reactive Forms.
As an example for Template Driven form:
and Reactive form:
For this an implementation of a directive using the ControlValueAccessor interface should be created.
Happy to create PR for this.
The text was updated successfully, but these errors were encountered: