Private services would be nice for multi-purpose modules

[mbenford]

When developing a component (a directive, a service etc) which is supposed to be used by another apps, it would be nice if some internal services (that are relevant to that component only) could be private, so they don't "leak" into the apps using the main component, which in turn would prevent them from clashing with other services defined in other modules.

The current workaround (which I believe is just common sense, not an official guideline) is to add some prefix to the name of those internal services in order to reduce the odds of them clashing, which IMO isn't ideal because it prevents one app from having nicely-named services (e.g, configuration).

What do you guys think?

Kind regards.

[btford]

This is something that will be addressed with 2.0's DI system.

I'm not sure if there's a great way to add this to Angular 1.x.

[mbenford]

Hi Brian.

Thanks for your input. Just out of curiosity, how will version 2.0 handle this? Did Vojta talk about it on his presentation about DI at ng-conf? If he did then I guess I've missed that part.

[btford]

yes; child injectors solve this