-
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
Show blank lines instead of N/A on service map popovers #57014
Conversation
Pinging @elastic/apm-ui (Team:apm) |
💔 Build Failed
To update your PR or re-run it, just comment with: |
6cd6b75
to
77da10b
Compare
💔 Build Failed
History
To update your PR or re-run it, just comment with: |
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
@elasticmachine merge upstream |
end, | ||
environment | ||
} | ||
} |
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.
nit: what do you think about collapsing small objects like this?
{
pathname: "/api/apm/service-map/service/{serviceName}",
params: {
path: { serviceName },
query: { start, end, environment }
}
};
(I wish there was a prettier setting for this...)
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 usually try to compress them but don't think too much about them.
); | ||
const isLoading = status === 'loading'; | ||
|
||
return <ServiceMetricList {...data} isLoading={isLoading} />; |
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.
Interesting approach with a fetcher component. Reminds me of Redux' "smart" and "dumb" components.
It results in an extra component - makes testing the inner component a lot more straightforward. So I'm all for it 👍
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 wanted to test out the scenarios in storybook without having to mock a bunch of requests. It makes that easier and I think it makes for a good pattern in some cases.
53310fd
to
92603aa
Compare
Because RUM agents never show CPU or memory usage, we don't want to always show the metric with N/A. If a metric is null, just hide the lines. Break up the display and fetching components and update the popover stories to show the list. Update some types.
157d185
to
f859192
Compare
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
* Show blank lines instead of N/A on service map popovers Because RUM agents never show CPU or memory usage, we don't want to always show the metric with N/A. If a metric is null, just hide the lines. Break up the display and fetching components and update the popover stories to show the list. Update some types. * Fix metric typings
) * Show blank lines instead of N/A on service map popovers Because RUM agents never show CPU or memory usage, we don't want to always show the metric with N/A. If a metric is null, just hide the lines. Break up the display and fetching components and update the popover stories to show the list. Update some types. * Fix metric typings
Because RUM agents never show CPU or memory usage, we don't want to always show the metric with N/A. If a metric is null, just hide the lines.
Break up the display and fetching components and update the popover stories to show the list.
Update some types.
Fixes #54405