-
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
[Fleet] Move settings to their own tab #117919
[Fleet] Move settings to their own tab #117919
Conversation
Pinging @elastic/fleet (Team:Fleet) |
…move-settings-to-their-tab
@@ -9,16 +9,12 @@ import React, { useEffect, useCallback } from 'react'; | |||
import styled from 'styled-components'; |
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.
This file is just the old settings flyout, that will be removed in coming PRs for multiple output UI
💛 Build succeeded, but was flaky
Test Failures
Metrics [docs]Public APIs missing comments
Async chunks
Page load bundle
History
To update your PR or re-run it, just comment with: cc @nchaulet |
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.
Tested locally, 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.
🚀
💚 Backport successful
This backport PR will be merged automatically after passing CI. |
Co-authored-by: Nicolas Chaulet <[email protected]>
Summary
As part of the multiple output UI we are moving the settings to their own tab #117317
Move the settings tab from a Flyout to a new tab in the Fleet application,
useUrlModal
hook as it's not use anymoreUI Changes