Replace style with css prop in Cloud Defend plugin
#202449
Merged
Conversation
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
albertoblaz
added
release_note:skip
|
Pinging @elastic/kibana-cloud-security-posture (Team:Cloud Security) |
|
@elasticmachine merge upstream |
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Async chunks
Page load bundle
cc @albertoblaz |
|
Starting backport for target branches: 8.x |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Dec 11, 2024
## Summary Part of the resolution of this issue: - elastic#149246 Removes the `style` prop in React components and elements to avoid using inline styles. Instead, it uses now the `emotion.css` prop to dynamically attach all styles to the native `class` attribute. ### Motivation Using inline styles at scale causes a performance penalty at rendering time. It's way more efficient to attach styles to a single or several classnames instead. ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) Co-authored-by: Elastic Machine <[email protected]> (cherry picked from commit c1addc9)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
Dec 11, 2024
…fend plugin (#202449) (#203809) # Backport This will backport the following commits from `main` to `8.x`: - [Replace `style` with `css` prop in Cloud Defend plugin (#202449)](#202449) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Alberto Blázquez","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-11T14:31:30Z","message":"Replace `style` with `css` prop in Cloud Defend plugin (#202449)\n\n## Summary\r\n\r\nPart of the resolution of this issue: \r\n- https://github.com/elastic/kibana/issues/149246\r\n\r\nRemoves the `style` prop in React components and elements to avoid using\r\ninline styles. Instead, it uses now the `emotion.css` prop to\r\ndynamically attach all styles to the native `class` attribute.\r\n\r\n### Motivation\r\n\r\nUsing inline styles at scale causes a performance penalty at rendering\r\ntime. It's way more efficient to attach styles to a single or several\r\nclassnames instead.\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\nCo-authored-by: Elastic Machine <[email protected]>","sha":"c1addc9ff78c4b5bb97938eee257e3ba0a200109","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Cloud Security","backport:prev-minor","backport:version","v8.18.0"],"title":"Replace `style` with `css` prop in Cloud Defend plugin","number":202449,"url":"https://github.com/elastic/kibana/pull/202449","mergeCommit":{"message":"Replace `style` with `css` prop in Cloud Defend plugin (#202449)\n\n## Summary\r\n\r\nPart of the resolution of this issue: \r\n- https://github.com/elastic/kibana/issues/149246\r\n\r\nRemoves the `style` prop in React components and elements to avoid using\r\ninline styles. Instead, it uses now the `emotion.css` prop to\r\ndynamically attach all styles to the native `class` attribute.\r\n\r\n### Motivation\r\n\r\nUsing inline styles at scale causes a performance penalty at rendering\r\ntime. It's way more efficient to attach styles to a single or several\r\nclassnames instead.\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\nCo-authored-by: Elastic Machine <[email protected]>","sha":"c1addc9ff78c4b5bb97938eee257e3ba0a200109"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202449","number":202449,"mergeCommit":{"message":"Replace `style` with `css` prop in Cloud Defend plugin (#202449)\n\n## Summary\r\n\r\nPart of the resolution of this issue: \r\n- https://github.com/elastic/kibana/issues/149246\r\n\r\nRemoves the `style` prop in React components and elements to avoid using\r\ninline styles. Instead, it uses now the `emotion.css` prop to\r\ndynamically attach all styles to the native `class` attribute.\r\n\r\n### Motivation\r\n\r\nUsing inline styles at scale causes a performance penalty at rendering\r\ntime. It's way more efficient to attach styles to a single or several\r\nclassnames instead.\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\nCo-authored-by: Elastic Machine <[email protected]>","sha":"c1addc9ff78c4b5bb97938eee257e3ba0a200109"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Alberto Blázquez <[email protected]>
CAWilson94
pushed a commit
to CAWilson94/kibana
that referenced
this pull request
Dec 12, 2024
## Summary Part of the resolution of this issue: - elastic#149246 Removes the `style` prop in React components and elements to avoid using inline styles. Instead, it uses now the `emotion.css` prop to dynamically attach all styles to the native `class` attribute. ### Motivation Using inline styles at scale causes a performance penalty at rendering time. It's way more efficient to attach styles to a single or several classnames instead. ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) Co-authored-by: Elastic Machine <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Part of the resolution of this issue:
stylewithemotion.css#149246Removes the
styleprop in React components and elements to avoid using inline styles. Instead, it uses now theemotion.cssprop to dynamically attach all styles to the nativeclassattribute.Motivation
Using inline styles at scale causes a performance penalty at rendering time. It's way more efficient to attach styles to a single or several classnames instead.
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:*label is applied per the guidelines