-
Notifications
You must be signed in to change notification settings - Fork 26.1k
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
refactor(devtools): create highlight overlay on node selection #60744
base: main
Are you sure you want to change the base?
refactor(devtools): create highlight overlay on node selection #60744
Conversation
Currently, highlighting works only when a directive explorer node is hovered. The change enables this feature on node selection as well.
@@ -57,12 +57,16 @@ import {serializeDirectiveState} from './state-serializer/state-serializer'; | |||
import {runOutsideAngular, unwrapSignal} from './utils'; | |||
import {DirectiveForestHooks} from './hooks/hooks'; | |||
|
|||
type InspectorRef = {ref: ComponentInspector | null}; |
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.
Any specfic reason for introducing this type instead of using ComponentInspector | null
directly ?
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.
Mainly for emphasizing and making it clear what's the role of this object. I added the type after the fact.
Edit: Also, the type is used in 2 places so it prevents minor repetition.
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?
Component highlighting works only when you hover a directive explorer node which is okay when you click on it but doesn't work when you use the keyboard to navigate through the tree.
What is the new behavior?
The change enables this feature on node selection as well.
cc @dgp1130
Screen.Recording.2025-04-04.at.13.23.18.mov
Does this PR introduce a breaking change?