-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Resolver/nodedesign 25 #60630
Resolver/nodedesign 25 #60630
Conversation
… into resolver/nodedesign
} | ||
|
||
for (const treeRoot of roots) { | ||
traverseLevels(idToAdjacent.get(uniquePidForProcess(treeRoot))!); |
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.
@oatkiller This is what I ended up replacing the level getter with. Should only touch each node in the tree once.
@oatkiller adjusted per your review. Thanks. |
@elasticmachine merge upstream |
traverseLevels(idToAdjacent.get(currentProcessMap.firstChild)!, nextLevel); | ||
} | ||
currentProcessMap.level = level; | ||
return void 0; |
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.
is this needed? seems like you could remove
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.
Typescript was whining about the function not returning anything. If you don't like the oldschool void 0
I could just make it undefined
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.
i think if you make the type its returning void instead of unknown it'll fix that
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.
that works even better; thanks @dplumlee
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.
⚡️ 1a1bc07
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.
awesome job
@elasticmachine merge upstream |
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
This reverts commit dd93a14.
This reverts commit 427bee4030137f7c0d99575dc847f00f08697266.
Issue(s)
https://github.com/elastic/endpoint-app-team/issues/104
Summary
This PR adds a basic layout to build on for Resolver nodes (following the "25% zoom configuration that was laid out by @lindseypoli and @marrasherrier ") that scales with the
camera
facilities provided by the Pan/Zoom selectors and state. It incorporates EUI color palette functions for shading (and creates space for arbitrage and the provision of more complex paint servers like gradients, patterns, etc. in/defs.tsx
) and an "Adjacency Map" that can be used to fulfill the navigation requirements for a "tree" as defined by https://www.w3.org/WAI/PF/aria/roles#treeAs it appears "embedded" in Alert Details:
Zoomed out:
Zoomed in:
Checklist
Delete any items that are not applicable to this PR.