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

[Watcher] Refine copy and layout of Watch History detail panel. #35462

Merged

Conversation

cjcenizal
Copy link
Contributor

This PR also internationalizes some copy.

image

@cjcenizal cjcenizal added non-issue Indicates to automation that a pull request should not appear in the release notes Feature:Watcher Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more labels Apr 23, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/es-ui

@elasticmachine
Copy link
Contributor

💔 Build Failed

Copy link
Contributor

@alisonelizabeth alisonelizabeth left a comment

Choose a reason for hiding this comment

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

@cjcenizal fixes look great! I left a couple comments. Two are unrelated to your changes, but just something I noticed while reviewing.


<EuiSpacer size="s" />

<EuiCodeBlock language="javascript">{executionDetail}</EuiCodeBlock>
Copy link
Contributor

Choose a reason for hiding this comment

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

what do you think about changing the language prop to json?


<EuiInMemoryTable
items={(itemDetail.watchStatus as any).actionStatuses}
itemId="id"
Copy link
Contributor

Choose a reason for hiding this comment

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

is this needed?

<FormattedMessage
id="xpack.watcher.sections.watchHistory.watchHistoryDetail.title"
defaultMessage="Executed on {date}"
values={{ date: itemDetail.startTime}}
Copy link
Contributor

Choose a reason for hiding this comment

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

getting a linting error here

Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Contributor

@bmcconaghy bmcconaghy left a comment

Choose a reason for hiding this comment

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

LGTM, nice tweaks for the copy here. I think things are clearer now.

@alisonelizabeth
Copy link
Contributor

@cjcenizal One other thing I just thought of :) We should probably update the simulation flyout as well to align. (It doesn't have to be this PR, just mentioning it here.)

Screen Shot 2019-04-23 at 9 42 17 AM

@elasticmachine
Copy link
Contributor

💔 Build Failed

@cjcenizal
Copy link
Contributor Author

Thanks for your review @alisonelizabeth! I've implemented your suggestions. Here's how the UI looks now:

image

@cjcenizal
Copy link
Contributor Author

@alisonelizabeth I'll work on that simulation flyout next. Thanks for mentioning that!

@elasticmachine
Copy link
Contributor

💔 Build Failed

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@cjcenizal cjcenizal force-pushed the watcher/history-flyout-padding branch from 69ef929 to 7a94157 Compare April 23, 2019 20:25
@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@cjcenizal cjcenizal merged commit 96ee395 into elastic:watcher-port Apr 23, 2019
@cjcenizal cjcenizal deleted the watcher/history-flyout-padding branch April 23, 2019 21:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Watcher non-issue Indicates to automation that a pull request should not appear in the release notes Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants