Is there another way how to handle circular dependencies in Angular service than by using $injector.get()?
Is require.js the right choice?
Asked
Active
Viewed 47 times
0
Amio.io
- 20,677
- 15
- 82
- 117
-
Why not refactor so you don't have circular dependencies? – Joey Ciechanowicz Apr 12 '16 at 11:08
-
As it is not always possible to keep the code nicely readable and structured. – Amio.io Apr 12 '16 at 11:09
-
No, there's no way. Yes, it's the right choice. – Estus Flask Apr 12 '16 at 11:22
-
@estus Sorry, estus, I don't what is your NO and YES for... – Amio.io Apr 12 '16 at 11:25
-
I am trying to get rid off the circular deps. It really separates concerns more. – Amio.io Apr 12 '16 at 11:29
-
@JoeyCiechanowicz Please have a look at my answer. Maybe you can give me a better advice. Thx. – Amio.io Apr 13 '16 at 07:06
-
@estus I have just realized what you meant with your comment. Thx. – Amio.io Apr 13 '16 at 07:26
-
Sometimes circular depencies just happen, for instance if you want to configure an $http interceptor and use ui-router to redirect, you will have a circular dependency. Just use $injector.get(). You just need to be carefull that it happen only when you really need it. – Walfrat Apr 22 '16 at 07:14
-
@Walfrat I do agree. By now I could really remove all `$injector.get()` by separating concerns better. – Amio.io Apr 22 '16 at 07:49
1 Answers
-2
Tip: Never inject anything except other models into your models or you end up with circular dependencies.
Amio.io
- 20,677
- 15
- 82
- 117