Expose debug info for batarangle

[tbosch]

For tooling, we need to expose more debug information.

• Expose RouteRegistry:
  • Tools can't just rely on the annotations as applications can register routes during runtime as well.
  • E.g. expose the RouteRegistry token via ng.probe.coreTokens['RouterRegistry'] so it can be read via DebugElement.injector.get(...). Also, add getters to the RouterRegistry to read out the existing rules.
• Expose declaration parent element
  • needed as the parent element in the DOM might be different because of content projection
  • expose DebugElement.declarationParent which should return another DebugElement.
• Expose providers used to create the platform and application injector
  • needed to visualize the injector hierarchy.

[vicb]

@tbosch can this one be closed now ?

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