[✨ Triage] dotnet/aspire#10048 by DamianEdwards - Dashboard should visually differentiate when args are escaped

[MihuBot]

Triage for microsoft/aspire#10048.
Repo filter: area-dashboard issues.
MihuBot version: 1a6438.
Ping MihaZupan for any issues.

This is a test triage report generated by AI, aimed at helping the triage team quickly identify past issues/PRs that may be related.
Take any conclusions with a large grain of salt.

dotnet/aspire#10048: Dashboard should visually differentiate when args are escaped by DamianEdwards
[Tool] Searching for dashboard escaped args, dashboard argument visualization, AddExecutable arguments, dashboard command line args, dashboard whitespace arguments (IncludeOpen=True, IncludeClosed=True, IncludeIssues=True, IncludePullRequests=True, Repository=dotnet/aspire)
[Tool] Found 101 issues, 27 comments, 101 returned results (14057 ms)

Here are the most relevant related issues and discussions for issue #10048 ("Dashboard should visually differentiate when args are escaped"):

---

1. Issue #6585 (November 2024) - Improvements to command line args display in the dashboard

• Summary: This issue notes that command line arguments for executable resources are not displayed with spaces next to the entry point command, making it hard to visually parse. It also mentions that the "open in visualizer" feature doesn't include the command line arguments.
• Resolution: Fixed by PR #6619 (see below).

---

2. PR #6619 (November 2024) - Fix source column displaying executable args

• Summary: This PR directly addresses the display of executable arguments in the dashboard, improving how they are shown in the source column. The after-screenshot shows arguments are now visually separated, making it easier to distinguish them.
• Relevance: This is highly related to your issue, as it improves the visual differentiation of arguments, though it does not specifically address escaping or whitespace in a way that highlights "escaped" args.

---

3. Issue #5570 (September 2024) - The dashboard does not show command line arguments for project resources

• Summary: Notes that command line arguments should be shown for project resources, similar to how they are for executables.
• Resolution: Fixed by PR #6212 (see below).

---

4. PR #6212 (October 2024) - Show command line arguments for project resource types

• Summary: Improves the dashboard to show command line arguments for both projects and executables, and enhances the text visualizer to show the entire command.
• Discussion: There is some discussion about how the arguments are displayed, but no mention of visually differentiating escaped arguments.

---

5. Issue #1226 (December 2023) - Executable should show resolved args

• Summary: Suggests that the dashboard should show the effective (resolved) arguments, not just the raw ones, in the details pane.
• Discussion: This is about showing the actual arguments after substitution, not specifically about visualizing escaping.

---

6. Issue #71 (October 2023) - Add a view command line args option to executables

• Summary: Requests a way to easily see the arguments for executables in the dashboard.
• Resolution: Addressed by PR #155 (see below).

---

7. PR #155 (October 2023) - Add working directory/args to executables page

• Summary: Adds sorting and filtering on working directory and arguments for executables in the dashboard.
• Relevance: Improves visibility of arguments, but not specifically about escaping.

---

8. Issue #4550 (June 2024) - Dashboard trims spaces included in a project's name

• Summary: Discusses how the dashboard collapses whitespace in project names due to HTML rendering, which is tangentially related to whitespace handling in the UI.
• Resolution: Determined to be a rendering issue, not a data issue.

---

9. Issue #9047 (May 2025) - Executable Arguments on dashboard show raw manifest expression

• Summary: Reports that after an upgrade, the dashboard shows raw manifest expressions in the arguments list, rather than the resolved values.
• Relevance: Related to how arguments are displayed, but not specifically about escaping or visual differentiation.

---

10. PR #1332 (December 2023) - Add copy to clipboard option for project/executable source columns

• Summary: Adds a copy-to-clipboard feature for the source column, and changes the display so the entire command appears the same (removes subtext for args).
• Discussion: There is some discussion about how to visually differentiate the executable name from the arguments, referencing PowerShell's colorization for visual scanning, but no specific solution for escaped arguments.

---

Summary

• There have been several improvements to the dashboard's display of command line arguments for both executables and projects, including better separation and visibility (see #6585, #6619, #6212).
• There is ongoing discussion about how to visually differentiate the executable name from its arguments, but no existing issue or PR specifically addresses the visualization of "escaped" arguments (i.e., those with whitespace or that are passed as a single string and thus escaped).
• The closest related discussions are about general argument visibility, resolved vs. raw arguments, and whitespace collapsing in project names, but not about the specific UX feature you are requesting.

Conclusion:
Your issue (#10048) is a new feature request that is not currently covered by any existing issue or PR. It is related to recent improvements in argument display, but the specific need to visually differentiate escaped arguments (e.g., by showing quotes or special formatting for single-string args) is not addressed elsewhere.

---

Related issues and PRs for further reading:

• #6585, PR #6619
• #5570, PR #6212
• #1226
• #71, PR #155
• #4550
• #9047
• PR #1332

Let me know if you need a more detailed summary of any specific discussion!