-
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
[Uptime] Step Details Page navigation - handle unequal steps between check groups #106289
[Uptime] Step Details Page navigation - handle unequal steps between check groups #106289
Conversation
Pinging @elastic/uptime (Team:uptime) |
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.
Tested this locally, not seeing the issue anymore! LGTM!
|
||
const step = steps.find((stepF) => stepF.synthetics?.step?.index !== expandedRowKey)!; |
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 knew!
it.
|
||
// expect only one accordion to be expanded | ||
expect(Object.keys(result.current.expandedRows)).toEqual(['0']); | ||
}); |
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.
Great job on this test 👍
…tails page in Uptime (elastic#106289)
…tails page in Uptime (elastic#106289)
Fixes #106248
When navigating between different checks on the step details page, we attempt to preserve the state of the accordion, keeping the appropriate accordion open as the user navigates. This can cause issues when there is an unequal amount of steps between each check, causing an unhandled reference error.
This PR adds additional defense to prevent this error.
Steps for testing: