-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
Move ui/notify banners to New Platform #43610
Conversation
💔 Build Failed |
💔 Build Failed |
Pinging @elastic/kibana-platform |
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.
SASS file moves lgtm
💔 Build Failed |
b117311
to
657f0e0
Compare
💔 Build Failed |
💔 Build Failed |
💔 Build Failed |
💚 Build Succeeded |
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.
Looks great!
2cba693
to
47b2d55
Compare
Pushed up some updates to run tests before I leave for the weekend. There's still a bit of work to do on testing the priority sorting. |
💔 Build Failed |
47b2d55
to
926ec38
Compare
ac72923
to
f95b8dd
Compare
💚 Build Succeeded |
f95b8dd
to
5892f15
Compare
💚 Build Succeeded |
💚 Build Succeeded |
Merging so we can this backported for 7.4 BC |
💔 Build Failed |
Summary
Fixes #41986
Fixes #44928
This moves the Banner APIs and React Component to Core.
For the time being, the actual rendering of the component is still in the legacy platform. This is left in order to side-step layout problems by moving the rendering outside the
app-wrapper
parent div.Dev Docs
Client-side New Platform plugins may now register global banners using the
core.overlays.banners
API:Checklist
Use
strikethroughsto remove checklist items you don't feel are applicable to this PR.For maintainers