You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Full instructions for how to do this audit can be found #199715, but the AC checklist has been copied here, with links to the relevant sections of that issue.
This issue pertains to just the following paths in the 'infra' plugin:
/x-pack/solutions/observability/plugins/infra/public/alerting (where these files have just been moved)
/x-pack/plugins/observability_solution/infra/public/alerting (where these files used to be - this shouldn't be relevant anymore but just in case!)
Acceptance criteria for the Infra plugin's alerting UI
Please break this into two issues and PRs if that's easier, so long as we cover both plugins with our best effort.
Important
Things marked as Required must be completed. Everything else we would really like teams to give their best effort to resolve, but are ultimately non-blocking.
Important details on each of these steps is noted in the main issue which has been linked to via each step's "details" link, but these "details" links reference HTML anchors in the linked issue and may require reloading the page in order to have the browser navigate correctly to the anchor position.
(Required) All usages of "success" colors have been updated to "accentSecondary" and "textAccentSecondary" as needed (details).
(Required) All usages of "successText" colors have been updated to "textAccentSecondary" as needed (details).
(Required) All references to renamed tokens have been updated to use the new token name. (details)
(Required) All usage of color palette tokens and functions now pull from the theme, and correctly update to use new colors when the theme changes from Borealis to Amsterdam and vice versa. (details)
Warning
Please be careful when removing styled components / moving to Emotion. These changes require tooling changes that can produce major problems in Kibana. If you do remove styled components from any files, they should be individually removed from the styled_components_files.js registry file, but please check the status of this PR to see whether there is a script to be run to generate that file from all of the current places where style components are imported in Kibana.
Follow up tasks to be completed later
These were originally part of the AC of this issue, but have since been de-scoped. I leave them here for future reference.
@kkurstak or @patpscal has reviewed the UI with the new changes and is ready to ship.
All usages of vis colors for non-visulalization usage have been removed in favor of other EUI color tokens, where possible. (details)
All "Custom colors" have been replaced with EUI color tokens. (details)
All usages of color functions have been removed in favor of color tokens, where possible. (details)
All usages of JSON tokens have been removed in favor of color tokens, where possible. (details)
The text was updated successfully, but these errors were encountered:
Full instructions for how to do this audit can be found #199715, but the AC checklist has been copied here, with links to the relevant sections of that issue.
This issue pertains to just the following paths in the 'infra' plugin:
Acceptance criteria for the Infra plugin's alerting UI
Please break this into two issues and PRs if that's easier, so long as we cover both plugins with our best effort.
Important
Things marked as Required must be completed. Everything else we would really like teams to give their best effort to resolve, but are ultimately non-blocking.
Important details on each of these steps is noted in the main issue which has been linked to via each step's "details" link, but these "details" links reference HTML anchors in the linked issue and may require reloading the page in order to have the browser navigate correctly to the anchor position.
Warning
Please be careful when removing styled components / moving to Emotion. These changes require tooling changes that can produce major problems in Kibana. If you do remove styled components from any files, they should be individually removed from the styled_components_files.js registry file, but please check the status of this PR to see whether there is a script to be run to generate that file from all of the current places where style components are imported in Kibana.
Follow up tasks to be completed later
These were originally part of the AC of this issue, but have since been de-scoped. I leave them here for future reference.
The text was updated successfully, but these errors were encountered: