-
Notifications
You must be signed in to change notification settings - Fork 693
Show exception details in text visualizer dialog #6230
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
Conversation
Yes please! |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
I would love this in 9 |
@JamesNK @davidfowl @DamianEdwards I moved the icon to the right side, so it sits with the masking button and the "..." dropdown button. See updated screenshots in PR description. |
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 like it.
One extra suggestion is to add an action to the menu here:
If there is an exception message then add a menu item with <icon> Exception details
and launches the same visualizer. The Log message
menu item already does the same thing.
If it is difficult then create a follow up issue. Stick with this for now and add the menu item in 9.1.
Adding a menu item makes sense, though it might reasonably be expected in the I was tempted to pull out an abstraction for these buttons and menu items, to take a more data-driven approach. I would rather do that in 9.1, to keep the scale of the change down. |
We'd need to add a way to add items to the grid value menu. It's doable, and I like the consistency, but not as high value. Structured logs will get a lot of use. Could do it properly in 9.1. |
Fixed in 340124a. |
@JamesNK what do you think of this: The filled icon looks a bit strange, but there's no regular version of that icon as far as I can tell. |
I see one in the FluentUI explorer: |
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).
340124a
to
6bb0b37
Compare
I'll do the menu item in a follow-up PR for 9.1. |
/backport to release/9.0 |
Started backporting to release/9.0: https://github.com/dotnet/aspire/actions/runs/11454378085 |
Description
Fixes #6130
Exception details are shown behind a button in two places:
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
:FluentHighlighter
when the text to highlight is empty, which will be the common case.MaxDisplayLength
. We never set this property, and it used space on everyGridValue
instance, and we create a lot of these objects.Here's how it looks for health checks:
Here's how it looks on mouse-over, along with a tooltip. The button appears too close to the text here, but that's consistent with other inline lightweight buttons. It only shows on mouse over. If we add more margin, it looks bad when the mouse isn't hovering over it.
Clicking the button opens the text visualizer we use throughout the dashboard:
Here's how it looks in structured logs:
Checklist
<remarks />
and<code />
elements on your triple slash comments?Microsoft Reviewers: Open in CodeFlow