4 ms·
I'm working on my first Angular2 app (inside Ionic 2) and have not been overly impressed. Most (all) of these will be first-project-pain but I'll list them anyw
by porker 10y ago
I'm working on my first Angular2 app (inside Ionic 2) and have not been overly impressed. Most (all) of these will be first-project-pain but I'll list them anyway:
* The massive coupling in app.module.ts and app.component.ts
* Coming as a backend dev, the coupling of services to the view layer
* Terminology of service/provider, and the general standard of documentation (3rd parties are far better than the official docs)
* Having a definite 'Angular way' of doing things, but not documenting it explicitly
And new to a modern JS project:
* Observables need a mindshift,and I'm still adjusting
* Keeping clean separation between layers. Subscribing to events to update viewmodel attributes helps, but I feel I'm lacking separation and over-coupling
Of the example code samples I've adapted, I've found the Aurelia community to be consistently high quality and well thought through, which can't be said for Angular.
- ssijak 10y ago"* Having a definite 'Angular way' of doing things, but not documenting it explicitly" Here you go https://angular.io/docs/ts/latest/guide/style-guide.html https://angular.io/docs/ts/latest/guide/style-guide.html
- oblio 10y agoI have a feeling that the Angular 2 docs are still a work in progress. For a long time, for example, the testing docs were still unfinished, even after the release.