-
Notifications
You must be signed in to change notification settings - Fork 21
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
Can't bind to 'formControl' since it isn't a known property of 'search-select'. #4
Comments
Hello. It's hard to tell exactly what is wrong with just a few snippets of code. But my guess from this message is that it has little to do with |
example module import here: https://github.com/OasisDigital/angular-material-search-select/blob/master/src/app/app.module.ts#L64 |
Ow you are probably right, I thought these modules where imported by your module internally already. Yea a small usage/getting started could help. |
They are probably imported inside the module and used there, but since you are using [formControl] from "outside" as you would with any other form control, I think it makes the most sense to import it in the usual way. I have an idea though, to make a standalone example on StackBlitz, to make it easier to get started. (It's also possible it might become moot, it sounds like the Angular Material team is eventually going to add some kind of search-select-like capability, eventually. If they do I will aim to upgrade this code to use it, if this code is still necessary.) |
Hi,
I try to use your project. But I'm getting an error and I don't know what to do.
Expected behavior: I can use the search-select together with the
formControl
attribute.Actual behavior: I'm getting a blocking error when I try to use
search-select
within my HTML.I did add the SearchSelectModule to my own module file (my.module.ts) like so:
And defined the local variables in one of the components: my-detail/my-detail.component.ts:
This is the only error I get:
What do I wrong!? There is no compile error.
Kind regards,
Melroy van den Berg
The text was updated successfully, but these errors were encountered: