-
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] Implement Settings new design for fleet server hosts #118385
Conversation
14d5931
to
45bfde4
Compare
}) => { | ||
const { docLinks } = useStartServices(); | ||
|
||
const form = useFleetServerHostsForm(fleetServerHosts, onClose); |
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.
@kpollich @joshdover I am wondering if this is good enough for separating business and presentation logic or if we should push this further and have a container component that calls that hooks and have really pure presentation component and pass this as props to this component?
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.
Personally I'm in favor of the approach you've already implemented here. I don't think a container component would add much value in this particular case, as it'd mostly just serve to pass the form
data returned from this hook down into the child component.
I was looking at the synthetics UI extensions for Fleet recently and I thought the component/hook patterns were well done. https://github.com/elastic/kibana/tree/main/x-pack/plugins/uptime/public/components/fleet_package
45bfde4
to
ee48337
Compare
Pinging @elastic/fleet (Team:Fleet) |
dd04102
to
a904559
Compare
a904559
to
02cd376
Compare
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.
Ran through everything locally and LGTM besides a few very minor typos/nits. 🚀
...s/fleet/public/applications/fleet/sections/settings/components/hosts_input/index.stories.tsx
Show resolved
Hide resolved
.../fleet/sections/settings/components/fleet_server_hosts_flyout/use_fleet_server_host_form.tsx
Outdated
Show resolved
Hide resolved
x-pack/plugins/fleet/public/applications/fleet/sections/settings/hooks/use_confirm_modal.tsx
Outdated
Show resolved
Hide resolved
💛 Build succeeded, but was flaky
Test Failures
Metrics [docs]Module Count
Public APIs missing comments
Async chunks
Page load bundle
History
To update your PR or re-run it, just comment with: cc @nchaulet |
💚 Backport successful
This backport PR will be merged automatically after passing CI. |
#118585) Co-authored-by: Nicolas Chaulet <[email protected]>
Summary
More progress on #117317
In the effort to refacto the new settings tab, that PR implement the new design for the fleet server hosts section.
Done in that PR:
Todo
UI Changes