Skip to content
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

[ML] Kibana Management Jobs list: Ensure proper title, tagline, and link to documentation #43418

Conversation

alvarezmelissa87
Copy link
Contributor

@alvarezmelissa87 alvarezmelissa87 commented Aug 16, 2019

Summary

Follow up to #43151

image

image

Checklist

Use strikethroughs to remove checklist items you don't feel are applicable to this PR.

For maintainers

- [ ] This was checked for breaking API changes and was labeled appropriately
- [ ] This includes a feature addition or change that requires a release note and was labeled appropriately

@alvarezmelissa87
Copy link
Contributor Author

Any feedback on the documentation links or particular language used is always welcome 😄
cc @sophiec20

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Copy link
Contributor

@sophiec20 sophiec20 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - but limited review of screenshots only.

Copy link
Contributor

@walterra walterra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to keep the useRefreshInterval() at the top level, happy to discuss alternatives.

// Call useRefreshInterval() after the subscription above is set up.
useRefreshInterval(setBlockRefresh);

if (isManagementTable === false) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hooks need to be at the top level, we cannot put them inside conditions unfortunately https://reactjs.org/docs/hooks-rules.html#only-call-hooks-at-the-top-level.

Maybe an alternative is to pass isManagementTable on to the hook and act on it there?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That makes sense normally, but in this case isManagementTable value is never changing so it wouldn't change the order of the hooks being called. 🤔
I'm happy to change it though since maybe it does set an example for a pattern we wouldn't want to follow most of the time.

@cchaos
Copy link
Contributor

cchaos commented Aug 19, 2019

Just a quick design nit, but having the Refresh button in a row by itself creates some weird spacing issues. Since the button is tightly coupled with the data in the table, I'd suggest moving the button to be within the table's toolbar and make it a filled button.

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Copy link
Member

@jgowdyelastic jgowdyelastic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@elasticmachine
Copy link
Contributor

💔 Build Failed

@elasticmachine
Copy link
Contributor

💔 Build Failed

@alvarezmelissa87
Copy link
Contributor Author

retest

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Copy link
Contributor

@walterra walterra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Latest changes LGTM

@alvarezmelissa87
Copy link
Contributor Author

@cchaos - Thank you for taking a look! 😄 The Refresh button placement is there to be consistent with the Job management page, with which it shares the table component (including the Refresh button).

We will be updating this view in subsequent iterations - it might be more appropriate then, depending on what other action buttons we add, to update the style for the Refresh button. For now I think keeping the experience consistent is what we're going for.

@alvarezmelissa87 alvarezmelissa87 merged commit cca899f into elastic:master Aug 20, 2019
@alvarezmelissa87 alvarezmelissa87 deleted the ml-in-kibana-management-updates branch August 20, 2019 15:37
alvarezmelissa87 added a commit that referenced this pull request Aug 20, 2019
…ink to documentation (#43418) (#43585)

* Update KM jobs list title and add tag line and link to docs

* add spaces column to analytics table for use in Kibana management

* add refresh button to kibana management analytics jobs list

* ensure refresh button does not cause bounce when loading

* move refreshInterval hook to page component

* add default value for analyticsTable prop
@elasticmachine
Copy link
Contributor

Pinging @elastic/ml-ui

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants