-
Notifications
You must be signed in to change notification settings - Fork 800
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
ThreatsDataViews: History fields preset #40580
Open
dkmyta
wants to merge
34
commits into
add/protect/core
Choose a base branch
from
add/components/threats-data-views-history-fields-preset
base: add/protect/core
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
34 commits
Select commit
Hold shift + click to select a range
3c24030
Init project branch
nateweller be99f50
Protect: Add Go to Cloud and Scan now button to Protect primary heade…
dkmyta 8dd5dde
Protect: Update Scan and History headers (#40058)
dkmyta 90d6898
Protect: de-emphasize cloud link by using link variant (#40211)
nateweller dd21913
Protect: add ShieldIcon component
nateweller 19c083e
Protect: Add ShieldIcon Component (#40402)
nateweller 08cdcb2
Protect: Integrate ThreatsDataViews Component (#40076)
nateweller 0a9047e
Components: Add ScanReport (#40419)
dkmyta aa9b8a3
Fix type errors
nateweller 08d8de3
Protect: Refactor AdminSectionHero (#40516)
nateweller b33c95a
Protect: Update Scan History extension types (#40548)
dkmyta e13aa74
Protect: Add Home page (#40317)
dkmyta 322819d
Protect: Integrate ScanReport (#40420)
dkmyta b397656
Add custom field set when viewing historic threats
dkmyta 8e1c8ae
Init project branch
nateweller 8a3dc9b
Protect: Add Go to Cloud and Scan now button to Protect primary heade…
dkmyta 1c4ba1e
Protect: Update Scan and History headers (#40058)
dkmyta ef21cc4
Protect: de-emphasize cloud link by using link variant (#40211)
nateweller 2f37bfc
Protect: add ShieldIcon component
nateweller ffdc98c
Protect: Add ShieldIcon Component (#40402)
nateweller 71384f1
Protect: Integrate ThreatsDataViews Component (#40076)
nateweller 4fccd4c
Components: Add ScanReport (#40419)
dkmyta f172be7
Fix type errors
nateweller d25db57
Protect: Refactor AdminSectionHero (#40516)
nateweller e86cfe1
Protect: Update Scan History extension types (#40548)
dkmyta 08d2ba1
Protect: Add Home page (#40317)
dkmyta 48fba20
Protect: Integrate ScanReport (#40420)
dkmyta ef6e5d0
Fix duplicate imports
nateweller 62838d3
ScanReport: Fix defaultLayout (#40603)
dkmyta a877b8c
Update onboarding popover placement (#40550)
dkmyta 7a47485
Adjust approach
dkmyta 87f5b71
Rebase
dkmyta 130eaf4
Fix JSDocs
dkmyta a1018bf
Rebase
dkmyta 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 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 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 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 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.
I am curious if there's a possible alternative configuration that would allow us to still include the "first detected" field regardless of the current filters, but hide/show the particular field in the table view based on the current filters, instead of omitting the definition of the fields entirely. I'll follow up on this!
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 had a similar hope, and did come across isVisible which I thought might be an option but seemed to not function as I expected it to.
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.
Could we use isVisible? Edit: ah, that might be a per-item method.
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 am working on a potential approach using the
onChangeView
callback, will share shortly!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.
Just a heads up that I did start with the onChangeView approach and it seemed to have its own limitations - IIRC there were challenges related to not being able to check the current view state against the changed view state because it was always outdated. Regardless, interested to see what you think might work reintroducing that take.