[SECURITY SOLUTIONS] [Case everywhere] Remaining cases removal work #96074
Labels
Feature:Cases
Cases feature
Team:Threat Hunting
Security Solution Threat Hunting Team
Theme: rac
label obsolete
Remaining cases removal work
Remaining moves
renderInvestigateInTimelineActionComponent
generic/reusable) [SECURITY SOLUTIONS] [Case everywhere] Move Insert Timeline functionality to Cases #94697 PR: [Security Solution][Cases] Re-enable timeline functionality #96496Bugs we made
Wrap all calls tomaybe not, follow this: https://elastic.slack.com/archives/CGK2KMWES/p1618856978042900?thread_ts=1618846558.042700&cid=CGK2KMWES uhh maybe not: After reviewing thecasesUi
inuseMemo
(followConnectorAddFlyout
/triggersActionsUi implementations)casesUi
calls we have in security_solution @chandlerprall advised that we keep these calls inline and move them touseMemo
"only if it's demonstrated to be a performance issue without.useMemo
/useCallback
usages includes some extra CPU&memory overhead and shouldn't be employed unless you can show the performance gain is worth the developer experience cost + that perf overhead". He also says "theuseMemo
way doesn't return a component, it directly returns the result oftriggersActionsUi.getAddConnectorFlyout
and injects that result"user_action_markdown.test.tsx
Steph WIP 4/21spyRoute
(pass as a prop or allow component to have children??) in case_view PR: [Security Solution][Cases] Fix cases breadcrumbs #97040Bugs we moved over
Refactors/Cleanup
refactor message storage to use storage from plugin.tsPR: [Security Solution][Cases] Update messages storage #97514isModal
property out ofAllCases
and break that logic out into its own component PR: [Security Solution] [Cases] All Cases Refactor & getAllCasesSelectorModal introduced #97149@cnasikas says:
The text was updated successfully, but these errors were encountered: