[4.x] Don't allow injecting classes without @Injectable  #13820

Activity

1. vicb

   added

   area: coreIssues related to the framework runtimeIssues related to the framework runtime

   open for contributionsAn issue that is suitable for a community contributor (based on its complexity/scope).An issue that is suitable for a community contributor (based on its complexity/scope).

   on Jan 7, 2017
2. trotyl commented on Jan 17, 2017

   

   trotyl

   on Jan 17, 2017

   Last edited by trotyl

   Contributor

   More actions

   I have a question of why making useClass so different?

   Would @Injectable() also be mandatory for useFactory when decorator for function expression implementation being ready?
   If so, is it a good way to use the same decorator reference to supporting two different decorator types?
   If not, why everything using useFactory/useValue... is injectable by default while what in useClass needs explicitly declared to be injectable?

   👍React with 👍1Reacted by Alexander Turtsevich
3. Toxicable commented on Apr 8, 2017

   

   Toxicable

   on Apr 8, 2017

   More actions

   Was this not fixed via b23ad39 ?
4. chuckjaz

   added

   flag: can be closed?

   on Apr 11, 2017
5. chuckjaz commented on Apr 13, 2017

   

   chuckjaz

   on Apr 13, 2017

   Contributor

   More actions

   Closed by #14931
6. chuckjaz

   closed this as completedon Apr 13, 2017
7. angular-automatic-lock-bot commented on Sep 11, 2019

   

   angular-automatic-lock-botBot

   on Sep 11, 2019

   More actions

   This issue has been automatically locked due to inactivity.
   Please file a new issue if you are encountering a similar or related problem.

   Read more about our automatic conversation locking policy.

   _{This action has been performed automatically by a bot.}
8. angular-automatic-lock-bot

   locked and limited conversation to collaborators on Sep 11, 2019