[Security Solution] expanded flyout - right section - table tab implementation#152303
[Security Solution] expanded flyout - right section - table tab implementation#152303PhilippeOberti merged 2 commits intomainfrom
Conversation
cb82e51 to
00396a8
Compare
dfd9e41 to
9a861e4
Compare
25355bc to
685eecd
Compare
|
Pinging @elastic/security-threat-hunting (Team:Threat Hunting) |
685eecd to
05205d3
Compare
| }); | ||
|
|
||
| describe('<TableTab />', () => { | ||
| it('should render table component', () => { |
There was a problem hiding this comment.
Is it worth testing that an actual field shows up in the table as well?
There was a problem hiding this comment.
I felt that it wasn't needed here as I'm using the existing EventFieldsBrowser component which already has some unit tests.
| browserFields={browserFields} | ||
| data={dataFormattedForFieldBrowser} | ||
| eventId={eventId} | ||
| isDraggable={false} |
There was a problem hiding this comment.
We need to determine what we do with this, as we'll have to pass some value for this for the flyout in the timeline context, though we'll probably want to take some time and look at the new timeline designs to figure out how we may want to treat this as well
There was a problem hiding this comment.
yeah that is something I need to be more aware of, at the moment I'm focusing only to the flyout from the alerts page, as I'm trying to get the complexity as low as possible...
|
|
||
| /** | ||
| * Table view displayed in the document details expandable flyout right section | ||
| * Table view displayed in the alert details expandable flyout right section |
There was a problem hiding this comment.
I think you were fine with document here as it would show for a regular event as well
There was a problem hiding this comment.
i didn't want to make this change, thanks for catching this!
|
Works well! I think it's worth discussing with design about using hover actions instead of the actions row in the table. Horizontal space is going to be really important for us here. |
michaelolo24
left a comment
There was a problem hiding this comment.
Looks good, just some nits, and some conversation about switching to hover actions
that is a really good point. I honestly didn't even think about it as I was reusing the existing |
2a8add4 to
d682cf2
Compare
d682cf2 to
83e6df4
Compare
💚 Build Succeeded
Metrics [docs]Async chunks
Unknown metric groupsESLint disabled line counts
Total ESLint disabled count
History
To update your PR or re-run it, just comment with: |
Summary
This PR leverages the work done in a previous PR and adds the table and json tabs to the Security Solution expandable flyout right section panel:
EventFieldsBrowsercomponent) with filtering and cell actions (filter in, filter out, add to timeline and copy to clipboard)How to test
xpack.securitySolution.enableExperimental: ['securityFlyoutEnabled']to thekibana.jsonfileyarn es snapshot --license trial,yarn test:generateandyarn start --no-base-pathRun tests and storybook
node scripts/storybook security_solutionto run Storybooknpm run test:jest --config ./x-pack/plugins/security_solution/public/flyoutto run the unit testsyarn cypress:open-as-cibut note that the integration/e2e tests have been written but are now skipped because the feature is protected behind a feature flag, disabled by default. To check them, add'securityFlyoutEnabled'hereScreen.Recording.2023-03-08.at.10.24.35.AM.mov
https://github.com/elastic/security-team/issues/6067
Checklist
Delete any items that are not applicable to this PR.