-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[Cases] Refactor: Move Case View Page main content to its own component #130666
[Cases] Refactor: Move Case View Page main content to its own component #130666
Conversation
Pinging @elastic/response-ops (Team:ResponseOps) |
Pinging @elastic/response-ops-cases (Feature:Cases) |
…lerts-tab-case-view
…lerts-tab-case-view
💚 Build SucceededMetrics [docs]Module Count
Async chunks
History
To update your PR or re-run it, just comment with: cc @academo |
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.
Tested and LGTM. Just left a comment about one of the test cases.
expect(result.getByTestId('case-view-status-action-button')).toBeTruthy(); | ||
}); | ||
|
||
it('should show a loading when initLoadingData is true and hide the user actions activity', () => { |
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 this read should show a loading indicator...
?
Summary
Partially addresses: #116501
First step to introduce a tabbed view in the case view page.
The current case view page component is too large to introduce a tabbed view without making it harder to maintain.
This simple refactor moves all the main content: user activity and sidebar to its own component along with all the required variables and hooks calls.
This PR doesn't affect user functionality or UI in anyway, only moves code around.
Checklist