-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[APM] Blank page when navigating to errors metadata #104322
[APM] Blank page when navigating to errors metadata #104322
Conversation
Pinging @elastic/apm-ui (Team:apm) |
@@ -157,9 +157,9 @@ export function DetailView({ errorGroup, urlParams }: Props) { | |||
<EuiTab | |||
onClick={() => { | |||
history.replace({ | |||
...location, | |||
...history.location, |
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.
It's a bummer that we can't catch this bug statically. This issue seems to be exactly that: microsoft/TypeScript#14306
This could be a solution:
microsoft/TypeScript#14306
But it looks like we are already setting no-restricted-globals
:
'no-restricted-globals': ['error', ...RESTRICTED_GLOBALS], |
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.
@sqren the rules is only applied for js files https://github.com/elastic/kibana/blob/master/packages/elastic-eslint-config-kibana/javascript.js#L10. I'm going to open a PR that adds this rule in the TS files https://github.com/elastic/kibana/blob/master/packages/elastic-eslint-config-kibana/typescript.js
Would be great if you can fix this, so it doesn't happen again (aka figure out if we can catch this statically with eslint/typescript) |
I'm gonna have it fixed on another PR. |
* using history.location instead of location * removing consoles
* using history.location instead of location * removing consoles
closes #104160