-
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
Preparation for High Contrast Mode, ML domain #205540
base: main
Are you sure you want to change the base?
Conversation
Pinging @elastic/appex-sharedux (Team:SharedUX) |
Pinging @elastic/obs-ux-management-team (Team:obs-ux-management) |
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]
History |
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.
ML changes LGTM
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.
LGTM, only obs-ux-infra-services changes
Summary
Reviewers: Please test the code paths affected by this PR. See the "Risks" section below.
Part of work for enabling "high contrast mode" in Kibana. See #205411
Background:
Kibana will soon have a user profile setting to allow users to enable "high contrast mode." This setting will activate a flag with
<EuiProvider>
that causes EUI components to render with higher contrast visual elements. Consumer plugins and packages need to be updated selected places where<EuiProvider>
is wrapped, to pass theUserProfileService
service dependency from the CoreStart contract.NOTE: EUI currently does not yet support the high-contrast mode flag, but support for that is expected to come soon. These first PRs are simply preparing the code by wiring up the
UserProvideService
.Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:*
label is applied per the guidelinesRisks
Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.
Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.
UserProfileService
dependency comes from the CoreStart contract. If acquiring the service causes synchronous code to become asynchronous, check for race conditions or errors in rendering React components. Code owners for this PR need to manually test the affected code paths.