I’ve definitely seen the need to mix properties with methods, and I don’t think this is a problem.
The goal is to clarify when and where developers are CREATING observables, and to minimize the times that this happens. If you have a
userInfo observable as a property and a
getPosts(id: string) method, it’s clearer to me that…
Hi there! I just gave this a try and found that running
ng new creates a package.json file that points at
@angular/core": "^4.2.4" which is right from a semantic versioning standpoint. The carrot means that the version should update across minor releases, meaning my npm install won’t install 4.2.4, it will install the latest minor & patch of Angular.
It’s important to remember that it’s not about beating anyone. We all want to make developers lives easier and to make the web a better place. We can all be successful and collaborate and learn from each other.
If you have custom webpack loaders, then you’ll want to keep using your custom configuration. If you are just using relatively standard ones (SASS/LESS, minifaction, bundling, typescript, AOT, etc) then you could definitely give switching to the CLI a try.
There’s a guide here: https://github.com/angular/angular-cli/wiki/stories-moving-into-the-cli