-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Observability plugin] Audit new EUI Borealis theme #204234
Conversation
Pinging @elastic/obs-ux-management-team (Team:obs-ux-management) |
/oblt-deploy |
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.
A few questions but otherwise token changes LGTM.
...k/plugins/observability_solution/profiling/public/components/topn_functions/function_row.tsx
Outdated
Show resolved
Hide resolved
...ervability_solution/infra/public/components/asset_details/tabs/processes/processes_table.tsx
Outdated
Show resolved
Hide resolved
...ins/synthetics/public/apps/synthetics/components/common/monitor_test_result/status_badge.tsx
Outdated
Show resolved
Hide resolved
Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services) |
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
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.
@fkanout We need to add the label backport:skip
and remove backport:prev-minor
.
Borealis changes should not be backported to 8.x
versions.
switch (status) { | ||
case ServiceHealthStatus.healthy: | ||
return theme.eui.euiColorVis0; | ||
return theme.colors.vis.euiColorVis0; |
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.
Fyi, vis colors changed. So especially for severity colors like this it means using the same mapping will change colors in Amsterdam. This might need alignment with a designer (not sure which is responsible here?), if that's expected or not.
See this related conversation about this topic.
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.
@mgadewoll, thanks for the heads up! @maciejforcone is our designer, but I don't think we can get his feedback soon enough for the PR due to the holiday period.
However, I chose the 1st option in the related conversation you mentioned. a.k.a using euiColorVisSuccess0
, euiColorVisWarning0
, and euiColorVisDanger0
@jasonrhodes please let me know if you think we need to do otherwise.
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.
Fyi, we're introducing new severity colors that should cover those cases across Kibana.
We can update to severity colors as follow-up.
x-pack/plugins/observability_solution/apm/public/components/shared/charts/timeseries_chart.tsx
Show resolved
Hide resolved
💔 Build Failed
Failed CI StepsTest Failures
Metrics [docs]Module Count
Async chunks
History
cc @fkanout |
@kdelemme @mgadewoll This PR seems to overlap with other ones scope-wise. I discussed this with @jasonrhodes, and we agreed to scope this PR to update only the files that are owned by our team. |
Hi @fkanout! To make our design review as helpful as possible, could you share from a final user's perspective where they might notice the changes (in case it impacts the user)? |
closing this in favor of #204615 |
Summary
It fixes #203338
Note
Some of the tokens have been ignored as they were on the server side or
common
folder, or they are coming from a shared package likepackages/react/kibana_context