-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
Looks like compatibility issue with Angular to 2.0.0-rc.5 #990
Comments
Reproduced to me |
Same here with rc.5 |
Resolved this problem.. @gaborkalmar and @meritor, How did you import material design modules? Did you import like as below? |
I did not import the ripple directive, that was it. Thanks. |
@inska OP is meritor, not merito. Correct to notify him. |
@merito Fixed. Sorry to bother you. |
See #973 |
Thanks a million.. No error, after importing this properly.
|
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:
Not sure, whether to call this a bug or feature request, as there is no mention of angular 2 version compatibility with 2.0.0-alpha.7-2 in material documents.
Actually, not sure whether the issue belongs here or should I raise this with Angular2 to keep the RC release backward compatible.
What is the expected behavior?
angular material component should work with latest release of angular 2
What is the current behavior?
Getting below error:
What are the steps to reproduce?
I know this won't help much, but, I don't know how to use plun
here is the template I am using
Tried with Plunker, but got lost in resolving script dependencies for rc.5.
That says, I don't know anything about Plunker.
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, browsers are affected?
Angular Version: 2.0.0-rc.5
Material Version: @angular2-material/button@2.0.0-alpha.7-2
OS: Windows 7
Browser Version: Google Chrome 52.0.2743.116 m
Is there anything else we should know?
The text was updated successfully, but these errors were encountered: