Router authorisation decorator

[aminebizid]

• I'm submitting a ...
• bug report
• feature request
• support request => Please do not submit support request here, see note at the top of this template.

Current behavior

Expected/desired behavior
A decorator preceding each route configuration:
@authorize(myFunc)

Where myFunc returns a Boolean

Cf WIF

• If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via
  https://plnkr.co or similar (you can use this template as a starting point: http://plnkr.co/edit/tpl:AvJOMERrnz94ekVua0u5).
• What is the expected behavior?
• What is the motivation / use case for changing the behavior?
• Please tell us about your environment:
• Angular version: 2.0.0-beta.X
• Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
• Language: [all | TypeScript X.X | ES6/7 | ES5 | Dart]

[ericmartinezr]

That's what CanActivate does in the deprecated router, that's most likely not to happen with the new new new router, we will have to see the design. Meanwhile search through github where CanActivate was discussed.

See #7784

[tbosch]

Activation is done via guards in the new router.

Closing this issue.

[angular-automatic-lock-bot]

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.}