Skip to content

Resolver/nodedesign 25#60630

Merged
bkimmel merged 66 commits intoelastic:masterfrom
bkimmel:resolver/nodedesign_25
Mar 23, 2020
Merged

Resolver/nodedesign 25#60630
bkimmel merged 66 commits intoelastic:masterfrom
bkimmel:resolver/nodedesign_25

Conversation

@bkimmel
Copy link
Contributor

@bkimmel bkimmel commented Mar 19, 2020

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#tree

As it appears "embedded" in Alert Details:
image

Zoomed out:
image

Zoomed in:
image

Checklist

Delete any items that are not applicable to this PR.

}

for (const treeRoot of roots) {
traverseLevels(idToAdjacent.get(uniquePidForProcess(treeRoot))!);
Copy link
Contributor Author

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.

@bkimmel
Copy link
Contributor Author

bkimmel commented Mar 21, 2020

@oatkiller adjusted per your review. Thanks.

@bkimmel
Copy link
Contributor Author

bkimmel commented Mar 23, 2020

@elasticmachine merge upstream

Copy link
Contributor

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

Copy link
Contributor Author

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

Copy link
Contributor

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

Copy link
Contributor Author

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

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚡️ 1a1bc07

Copy link
Contributor

@oatkiller oatkiller left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

awesome job

@bkimmel
Copy link
Contributor Author

bkimmel commented Mar 23, 2020

@elasticmachine merge upstream

@kibanamachine
Copy link
Contributor

💚 Build Succeeded

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@bkimmel bkimmel merged commit dd93a14 into elastic:master Mar 23, 2020
@bkimmel bkimmel deleted the resolver/nodedesign_25 branch March 23, 2020 21:18
bkimmel added a commit that referenced this pull request Mar 24, 2020
* Adds resolver zoomed-out process nodes for process tree
oatkiller pushed a commit to oatkiller/kibana that referenced this pull request Mar 30, 2020
oatkiller pushed a commit to oatkiller/kibana that referenced this pull request Mar 30, 2020
This reverts commit 427bee4030137f7c0d99575dc847f00f08697266.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Feature:Endpoint Elastic Endpoint feature Feature:Resolver Security Solution Resolver feature release_note:skip Skip the PR/issue when compiling release notes v8.0.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants

Comments