-
Notifications
You must be signed in to change notification settings - Fork 8.6k
[Security Solution] Prebuilt rule customizations flyout refactor #227355
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
Merged
Merged
Changes from all commits
Commits
Show all changes
19 commits
Select commit
Hold shift + click to select a range
61c6dd4
addresses previous comments
dplumlee a5d72a8
adds tests
dplumlee 22ccc28
Merge remote-tracking branch 'upstream/main' into prebuilt-reversion-…
dplumlee d90148b
fixes linting
dplumlee c1fd796
fixes linting
dplumlee 7ee2242
fixes test
dplumlee bf42bbd
Merge remote-tracking branch 'upstream/main' into prebuilt-reversion-…
dplumlee 48d7a3d
Merge remote-tracking branch 'upstream/main' into prebuilt-reversion-…
dplumlee e8e6a68
adds tests
dplumlee b94e6b9
fix test
dplumlee 6be6972
updates ui
dplumlee cb74710
Merge remote-tracking branch 'upstream/main' into prebuilt-reversion-…
dplumlee 94dccaa
remove unused code
dplumlee b06804c
update mock names
dplumlee 775c2be
fix name
dplumlee 8087a48
get rid of setCustomizationsRule action
maximpn ed0e22e
remove html native button hover
dplumlee 735935a
Merge remote-tracking branch 'davis/prebuilt-reversion-refactor' into…
dplumlee ccc74fd
Merge remote-tracking branch 'upstream/main' into prebuilt-reversion-…
dplumlee File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
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.
Should these live within this file, now, or do you intend to reuse them?
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 they are fine to live here for now, we don't display either of these fields this way anywhere else - they usually get split up into their own section or tab. I broke them out into the smaller fragment stubs for overall readability in the main component
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.
While these two components aren't explicitly reused they are actually reused, please check setup and note components from the Prebuilt Rule Upgrade Flyout.
Ideally we should reuse Investigation Guide and Setup Guide components. You may see some readonly components are defined in rule_definition_section.tsx.
notecomponent in the Prebuilt Rule Upgrade Flyout should be renamed toinvestigation_guide.nit: IMHO functions have higher readability
vs