4 ms·
I think you meant to say that you switched to Angular 2 with Angular Material 2 which still considers itself in alpha status which I would not currently use in
by adamduren 10y ago
I think you meant to say that you switched to Angular 2 with Angular Material 2 which still considers itself in alpha status which I would not currently use in production.
I agree that the documentation can be improved in that respect, however once you have learned the convention it applies for all components. In angular 1 documentation you had the same issues of `ngRepeat` and similar directives being expressed as `ng-repeat` in the HTML attributes. The only explanation is in the directive documentation [0] which can be pretty exhausting to take in.
[0]: https://docs.angularjs.org/guide/directive#normalization https://docs.angularjs.org/guide/directive#normalization
- hanspragt 10y agoNo, we used Polymer in an Angular 2 app. <- Sorry, I misunderstood what you were saying. Yeah, the full name is Material Design for Angular 2. Even though Material 2 is in alpha, the components we need just work better than in Polymer; They have fewer quirks, fewer bugs, and fit better into the Angular 2 ecosystem.
- adamduren 10y agoAh, I understand now. I've done some work integrating Angular 2 and Polymer and there are pitfalls. I've come across this repo in the past for integrating the two but I personally haven't used it yet. https://github.com/vaadin/angular2-polymer https://github.com/vaadin/angular2-polymer
- hanspragt 10y agoThe integration into Angular 2 was actually fairly seamless once I added vulcanize into the build process.