Skip to content
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

Merged
merged 6 commits into from
Apr 25, 2022

Conversation

academo
Copy link
Contributor

@academo academo commented Apr 20, 2022

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

@academo academo added Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Feature:Cases Cases feature v8.3.0 labels Apr 20, 2022
@academo academo self-assigned this Apr 20, 2022
@academo academo added release_note:skip Skip the PR/issue when compiling release notes backport:skip This commit does not require backporting labels Apr 20, 2022
@academo academo marked this pull request as ready for review April 20, 2022 11:57
@academo academo requested a review from a team as a code owner April 20, 2022 11:57
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops-cases (Feature:Cases)

@kibana-ci
Copy link
Collaborator

💚 Build Succeeded

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id before after diff
cases 396 398 +2

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
cases 287.7KB 288.5KB +841.0B

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @academo

Copy link
Contributor

@peteharverson peteharverson left a 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', () => {
Copy link
Contributor

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... ?

@academo academo merged commit 01130d1 into elastic:main Apr 25, 2022
@academo academo deleted the enhancement/cases-alerts-tab-case-view branch April 25, 2022 16:07
dmlemeshko pushed a commit to dmlemeshko/kibana that referenced this pull request May 5, 2022
kertal pushed a commit to kertal/kibana that referenced this pull request May 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:skip This commit does not require backporting Feature:Cases Cases feature release_note:skip Skip the PR/issue when compiling release notes Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) v8.3.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants