-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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 'errorStateMatcher' since it isn't a known property of 'input' #7694
Comments
html template:
|
This was a breaking change in beta.12. Instead of passing a function, you pass a class instance of type |
What is the better example to follow: or do they both work? |
Either way will work. I don't know which is better practice, but if you need access to some component state, that demo example is definitely the easiest. You can also do some DI trickery if you wish too, |
I am still getting the same error using:
with
I feel like I am missing something.. |
mdInput -> matInput Same goes for md-form-field |
Yep, that did it. Thanks guys! |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Bug, feature request, or proposal:
Seems like a bug..
What is the expected behavior?
For
errorStateMatcher
to bind to an input.What is the current behavior?
Can't bind to 'errorStateMatcher' since it isn't a known property of 'input'
What are the steps to reproduce?
Using angular material beta 12 and angular 4.4.4
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 4.4.4
Material 2.0.0-beta.12
Is there anything else we should know?
Just upgraded from beta 11 to beta 12 and with it had to upgrade to angular 4.4.4 but now for some reason I get
Can't bind to 'errorStateMatcher' since it isn't a known property of 'input'
in the browser console upon navigating to the app.I have both the forms module and reactive forms module in my application.
The text was updated successfully, but these errors were encountered: