TODOs on the Client side

[lirantal]

We have a few TODOs that were added, let's see if they make sense or clean them up:

• articles.client.controller.js#L34 - https://github.com/meanjs/mean/blob/master/modules/articles/client/controllers/articles.client.controller.js#L34
• users.client.service.js#L14 - https://github.com/meanjs/mean/blob/master/modules/users/client/services/users.client.service.js#L14

@mleanos would you like to take a stab at this?

[mleanos]

I've been thinking about this. Both TODO's have the potential to be big changes.

1. Articles client-controller: May need a big refactor of the service. This could be a first phase of exploring client-side models.
2. Users Admin client-service: This could require some back-end router changes; similar to @trainerbill's suggestion of using Express.router in each route configuration.

I'll look into both of these to see if I can come up with a good solution to each, and how much work/refactoring is involved.

[lirantal]

Ok so it's either we decide to fullfill the TODOs or we remove them from the code.
@ilanbiala , @codydaig to review if the TODOs are really necessary or not.

[ilanbiala]

Both seem valid, and I think they could just be a quick refactor. @mleanos for the first we could just move the code, right? For the second, it might be a bit more refactoring in other places where we use this, so I'm not sure how the dependencies would work out, but if they stay clean across modules then it shouldn't be an issue.

[lirantal]

One issue we tackled and merged.
Remaining issues?

[mleanos]

@lirantal This TODO can wait until after we release 0.5.0. This change will be a bit involved, and I'm still not sure how we want to go about it.

[lirantal]

Sure