-
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
Design cleanup of Uptime app #31663
Design cleanup of Uptime app #31663
Conversation
Pinging @elastic/kibana-design |
Pinging @elastic/uptime |
@@ -106,15 +106,17 @@ class Application extends React.Component<UptimeAppProps, UptimeAppState> { | |||
let colors: UptimeAppColors; | |||
if (darkMode) { |
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.
@cchaos Do you have a pattern for this kind of thing I could steal. I mostly just recolored what they had here, but it seems like a silly way to do this when the colors vars themselves are the same outside of the theme.
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.
I have not run into any theme vars imported via JSON in any of my fixes yet. You could ask SIEM or APM since I'm pretty sure they do. My initial thought would be to set the import path based on the global theme but I'm not exactly sure the way to do this.
💔 Build Failed |
💔 Build Failed |
Looking at your last comment, you can see that the white line indicating your hover point is lined up with the peaks of both the green and red series. There are a couple reasons for confusion but I'm not exactly sure what yours is.
|
Heh. Yeah, I was mostly questioning the data in the graph to your second point
This seems like a bug or is a really confusing way to present the data? |
💔 Build Failed |
💔 Build Failed |
💔 Build Failed |
💔 Build Failed |
💚 Build Succeeded |
💔 Build Failed |
💚 Build Succeeded |
it('returns expected result for no status filter', async () => { | ||
expect.assertions(2); | ||
const search = jest.fn(); | ||
search.mockReturnValue({ |
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.
snapshot rather than mock? might make maintenance easier
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.
Approved but would like to see component names not have Query in the name, and query object not having a prefix of "get" making it look like a method/getter
💔 Build Failed |
💔 Build Failed |
💚 Build Succeeded |
Summary
This does some reworking of the Uptime layouts to get them closer to the rest of Kibana.
Some comments
EDIT: resolves #29841.
also resolves #31831.
I need the following help
@justinkambic would love some help fixing the following. Couldn't find the code immediately to do this. Also, I couldn't get the snapshots to update. It would just hang.
Checklist
Use
strikethroughsto remove checklist items you don't feel are applicable to this PR.For maintainers