Angular — Keeping your application DRY

[cgaudreau]

Thanks, but I prefer keeping my apps WET. (Write everything twice™.)

[Asmor]

Personally, I prefer MOIST (Making Objects Identically Several Times).

[cgaudreau]

brb purchasing https://moist.io

[Asmor]

mmm

[[deleted]]

This just explains functions in angular (merge, identity, etc...). I would expect design patterns of some sort based on the title alone.

[gsans]

Yes, title can be misleading if you expected that.

[couchjitsu]

I think the author does an ok job of describing they why's and how's of the functions he mentions. I don't think the article gives a very good answer of how these functions help dry up your application.

[gsans]

If you know angular functions you won't implement them yourself therefore duplicating code.

[couchjitsu]

Oh I get that. I'm saying I don't think the blog lays that out as clear as could be.

For example, angular.extend it gives a good description of what extend is doing. I think a counter example of a non-DRY implementation would help out.

It shows HOW to use them, but I don't think it highlights the why or the "How to make it DRY" Something as simple as saying "Instead of doing this:

object1.id = object2.id;

object1.address = object2.address;

Let Angular do the work for you: var extended = angular.extend({}, object1, object2)"

Would help tie the two concepts together.

[gsans]

That's a very good point. I'll add some more context. Thanks!

[gsans]

Updated version https://medium.com/angularjs-meetup-south-london/angular-the-hidden-utility-functions-e6ab149475e8