I'm submitting a ... (check one with "x")

[ ] bug report => search github for a similar issue or PR before submitting
[ x ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior
Why resolves in routes executing after canActivate and canActivateChild? Some activate actions are based on the data returned by the calling in resolve. However, currently the canActivate and canActivateChild action will executed firstly before resolves. That is not reasonable, right?

Expected behavior

canActivate and canActivateChild action will executed after resolve returned.

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?
Session check etc.

Please tell us about your environment:
npm start

• Angular version: 2.0.X
  2.0.6

• 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 ]
  All browsers where this could be reproduced

• Language: [all]
  all

• Node (for AoT issues): node --version =
  v6.9.5