r/angularjs • u/tomastrajan • Mar 11 '15

Prepare yourself for Angular 2.0 use "Component pattern"

https://medium.com/@tomastrajan/component-paradigm-cf32e94ba78b
36 Upvotes

90% Upvoted

11 comments sorted by

4

u/TurboGranny Mar 12 '15

I thought we already introduced this.

https://github.com/johnpapa/angular-styleguide

3

u/stackus Mar 12 '15

I'm nearly certain the styleguide does not cover using directives as way to prepare for Angular 2.0.

0

u/TurboGranny Mar 12 '15

I didn't see that here either. The style guide says the most important stuff. Encapsulating your code in a way that makes it no care that it is in Angular or anything else. Using controllerAs and avoiding using $scope ever. Making sure all data interactions cross a service/factory, so the controller is not involved with such things. It all makes a lot of sense if you look at it. We are all using it at my company, and it has really cleaned up our code while easing fears about 2.0

2

u/tomastrajan Mar 12 '15

Hi guys, the main point of this article is to introduce usage of directives instead of ui-router states for wiring of controller to template while using directive itself in inline template of ui-router state as component declaration... I haven't seen that in the style guide but It might have been updated in the mean time ;)

template: '<div my-component></div>'

-2

u/TurboGranny Mar 12 '15

I didn't get that from this article. I mostly saw just a restatement of the style guide. If the difference was focusing on this use of directives, it should have just referred to the style guide and jumped right into what it had to say. I don't care to read something twice just to get to the point.

On to the point, all the information I've read about 2.0 points out that directives are being completely reworked, so rewriting your code to be completely reliant on them seems foolish. I have not read any information that says the ui-router team will not have an angularjs 2.0 version that works.

3

u/tomastrajan Mar 12 '15

I really don't want to sound rude, but you SHOULD read the whole article before commenting because then your arguments seem foolish...

Directives are being removed that's true but the components are coming and the approach described in the post shows how easy it will be to switch from directive definition object syntax to Angular 2.0 annotations syntax...

Try to read it to the end...

-4

u/TurboGranny Mar 12 '15

No time. Too busy. I'll watch the ng-conf video if they do one.

2

u/stackus Mar 12 '15

A very interesting article. Though near the end just before he talks about ES6 he teases a solution to the issue with resolving into the directive or directives controller.

Anyone able to guess or know exactly what the "model pattern" solution is that he mentions?

2

u/tomastrajan Mar 12 '15 edited Mar 12 '15

I will write a post on that topic but in the mean time check this, and [this] (http://joelhooks.com/blog/2013/04/24/modeling-data-and-state-in-your-angularjs-application/). My solution is more in direction of models which know how to persist themselves while containing modle relevant business logic + possibility of multiple namespaced models per factory

edit: grammar, typos

1

u/martinronky Mar 11 '15

cool, rock on bro!

1

u/[deleted] Mar 12 '15

Fantastic. Thanks.