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] Converts full time range selector control to EUI / React #35074

Merged

Conversation

peteharverson
Copy link
Contributor

@peteharverson peteharverson commented Apr 15, 2019

Summary

Converts the control for automatically setting the time filter to the full time range of the job to EUI / React.

image

Checklist

For maintainers

@elasticmachine
Copy link
Contributor

Pinging @elastic/ml-ui

@elasticmachine
Copy link
Contributor

💔 Build Failed

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

Copy link
Contributor

@alvarezmelissa87 alvarezmelissa87 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

@peteharverson peteharverson force-pushed the ml-full-time-range-selector-eui branch from 573d2a3 to 1178f2f Compare April 16, 2019 08:38
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.

LGTM, just added a question about returning from setFullTimeRange().

import { ml } from '../../services/ml_api_service';

export function setFullTimeRange(indexPattern: IndexPattern, query: Query) {
return ml
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we need the return here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No the return isn't needed. I'll remove it.

Copy link
Member

@jgowdyelastic jgowdyelastic Apr 16, 2019

Choose a reason for hiding this comment

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

The return was added in the original version so the promise chain could be used to trigger an update after the time range had been loaded.
I think this is a useful feature and is being currently being used by the new job wizards.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Well spotted @jgowdyelastic . The return is needed when prepopulating the job wizard settings when cloning a job that was created in the wizards. I have added it back in.

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@peteharverson peteharverson merged commit 55a63ea into elastic:master Apr 16, 2019
@peteharverson peteharverson deleted the ml-full-time-range-selector-eui branch April 16, 2019 11:06
peteharverson added a commit to peteharverson/kibana that referenced this pull request Apr 16, 2019
…c#35074)

* [ML] Converts full time range selector control to EUI / React

* [ML] Remove console log from time range selector service

* [ML] Fix linting errors in full time range selector ts files

* [ML] Switch to using I18nContext in wrapping directive

* [ML] Remove unnecessary return from setFullTimeRange

* [ML] Add setFullTimeRange return back in for clone job settings
peteharverson added a commit that referenced this pull request Apr 16, 2019
#35147)

* [ML] Converts full time range selector control to EUI / React

* [ML] Remove console log from time range selector service

* [ML] Fix linting errors in full time range selector ts files

* [ML] Switch to using I18nContext in wrapping directive

* [ML] Remove unnecessary return from setFullTimeRange

* [ML] Add setFullTimeRange return back in for clone job settings
walterra pushed a commit to walterra/kibana that referenced this pull request Apr 23, 2019
…c#35074)

* [ML] Converts full time range selector control to EUI / React

* [ML] Remove console log from time range selector service

* [ML] Fix linting errors in full time range selector ts files

* [ML] Switch to using I18nContext in wrapping directive

* [ML] Remove unnecessary return from setFullTimeRange

* [ML] Add setFullTimeRange return back in for clone job settings
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.

5 participants