Remove commas between endpoints in grid

[drewnoakes]

Description

The commas between endpoints are redundant as the underline of the anchor visually separates multiple entries. The comma visually collides with the underline, and looks a bit strange when there's only one item and the rest in overflow.

Subjective, but I think it looks a little sharper like this.

Before

After

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Link to aspire-docs issue:
  • No

Microsoft Reviewers: Open in CodeFlow

[JamesNK]

The commas between endpoints are redundant as the underline of the anchor visually separates multiple entries.

This won't be true for tcp endpoints. They're plain text.

However, maybe the space can be the delimiter. That shouldn't be a situation where an endpoint contains spaces.

[JamesNK]

@DamianEdwards @davidfowl @leslierichardson95 Opinions either way?

[drewnoakes]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[drewnoakes]

This won't be true for tcp endpoints. They're plain text.

True, some URLs won't be hyperlinked or underlined, but the space should still be clear.

[DamianEdwards]

Yeah I like this change

[adamint]

Agree that space is an acceptable delimiter here

[adamint]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[drewnoakes]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[drewnoakes]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[drewnoakes]

@adamint the test failure here seems related to health checks. Did we commit something that breaks tests?

Assert.Null() Failure: Value of type 'Nullable<HealthStatus>' has a value
Expected: null
Actual:   Healthy