[Security Solution][Entity details] - move prevalence related hooks to flyout folder#190109
Merged
PhilippeOberti merged 2 commits intoelastic:mainfrom Aug 19, 2024
Merged
Conversation
Contributor
|
Pinging @elastic/security-threat-hunting-investigations (Team:Threat Hunting:Investigations) |
019685f to
b5ffcdf
Compare
b5ffcdf to
a069946
Compare
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]Module Count
Async chunks
History
To update your PR or re-run it, just comment with: |
christineweng
approved these changes
Aug 19, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR continues the effort in removing all old flyout components, hooks and utils functions. It moves all the code related to prevalence and process tree for analyzer and other components from commone folders to the alert details expandable flyout folder
The goal of this PR is to:
The purpose of the PR was never to full refactor the code, so things that aren't necessarily super clean might still be present.
No UI changes should be visible whatsoever!
Checklist
https://github.com/elastic/security-team/issues/7462