-
Notifications
You must be signed in to change notification settings - Fork 26.6k
refactor(devtools): intergrate the TreeVisualizer into the TreeVisualizerHost component #63530
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
954c1e7
to
2144618
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No immediate concerns on my side, but I admit a lot of the router tree stuff goes over my head, so I'm not entirely following the change here. Maybe @AleksanderBodurri or @sumitarora could provide more meaningful feedback than I can?
@dgp1130, I hope that this timeline clarifies the purpose of this change:
|
…izerHost component Use the `TreeVisualizer` internally in the host component instead of managing these separately in their client components.
2144618
to
498fdbd
Compare
652ddc1
to
d1786f6
Compare
@if (routerDebugApiSupport()) { | ||
<div class="filter"> | ||
<input | ||
#searchInput |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@AleksanderBodurri, would it make sense to you to disable the tab from here instead:
I assume this check was added to cover the case when the router tree tab has been enabled in a previous session, but we don't have routes to show in the current one, since the switch in the settings menu is already rendered only if supportedApis.routes
is true.
…eVisualizerHost component
d1786f6
to
3608ae3
Compare
PR 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?
The
TreeVisualizer
is instantiated directly in the client components.What is the new behavior?
Use the
TreeVisualizer
internally in theTreeVisualizerHost
component instead of managing these separately in their client components (e.g. Injector and Router tree components/tabs).