Skip to content

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Oct 22, 2024

Backport of #6230 to release/9.0

/cc @drewnoakes

Customer Impact

  • Better support for diagnostics with a more consistent UX.
  • UI perf improvements.

Testing

Plenty of manual testing in addition to the automated tests.

Risk

Low. This UI component is contained.

Regression?

Microsoft Reviewers: Open in CodeFlow

Exception details are shown behind a button in two places:

1. In the "Message" column of the structured logs table, when an exception exists.
2. In the "Health reports" grid in resource details, when a health report includes exception details.

Previously, the stack trace would be shown in a popup when the mouse hovered over the icon, sort of like a tooltip.

This commit changes the behaviour so that exception details are shown in the existing text visualizer dialog whenever the icon is clicked.

The icon becomes a `FluentButton` for consistency with the menu button to the right of the cell.

Also some optimisations in `GridValue`:

- Don't use `FluentHighlighter` when the text to highlight is empty, which will be the common case. This improves UI performance.
- Remove `MaxDisplayLength`. We never set this property, and it used space on every `GridValue` instance, and we create a lot of these objects.
- Remove some redundant DOM elements.
- Support adding arbitrary buttons to the right-hand side of the area (used for the "exception details" button).
@joperezr
Copy link
Member

Low Risk, manual validation, and great improvement on experience. Approved for 9.0

@joperezr joperezr merged commit ea4aeb3 into release/9.0 Oct 22, 2024
8 checks passed
@joperezr joperezr deleted the backport/pr-6230-to-release/9.0 branch October 22, 2024 19:54
@github-actions github-actions bot locked and limited conversation to collaborators Nov 22, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants