refactor(devtools): add matcher and runGuardsAndResolvers support in …#65090
Conversation
|
#64938 isn't even merged, that changes is too premature ATM. |
As I understand it, |
|
I shouldn't be reviewing PRs so late, you're right. |
|
Will take over the review since Alex is not available. |
fb98b66 to
1554f3a
Compare
Yeah, that's something that we should handle. |
4cd7002 to
86dff60
Compare
|
Yeah, let's have |
|
@SkyZeroZx, we'll need a rebase since there is a conflict. Other than that, LGTM 👍 |
86dff60 to
88fa8a4
Compare
…router viewer Enhance the Angular DevTools router viewer to display routes that use custom `matcher` functions and reflect the `runGuardsAndResolvers` configuration
88fa8a4 to
73796a9
Compare
|
This PR was merged into the repository. The changes were merged into the following branches:
|
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |

…router viewer
Enhance the Angular DevTools router viewer to display routes that use custom
matcherfunctions and reflect therunGuardsAndResolversconfigurationPR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Other information
Question :

When a
matcheris used, thepathproperty is not allowed. However, in the router viewer, it currently displays as/undefined.We should consider replacing
/undefinedwith a more descriptive label.