Use Date Pipe for Angular Client

[giuliohome]

You should be using a date pipe in fetch-data.component.html at line 18, the fix is shown below

    <tr *ngFor="let forecast of forecasts">
      <td>{{ forecast.date | date }}</td>

or complete with time part

    <tr *ngFor="let forecast of forecasts">
      <td>{{ forecast.date | date :'medium' }}</td>

It looks quite better - either just a date

or date and time -

than the original vanilla version in ISO format

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 32a18270-91cd-2a02-2eb8-2c8b1ed03737
• Version Independent ID: c58d57e5-a0c2-201d-f6dd-076ad5971fcb
• Content: Use the Angular project template with ASP.NET Core
• Content Source: aspnetcore/client-side/spa/angular.md
• Product: aspnet-core
• Technology: aspnetcore-clientside
• GitHub Login: @SteveSandersonMS
• Microsoft Alias: stevesa

[serpent5]

@Rick-Anderson Should this be transferred to the https://github.com/dotnet/spa-templates repo?

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[mkArtakMSFT]

Thanks for contacting us. @giuliohome feel free to send us a PR with the proposal.
We'll get someone to review it next week.

[giuliohome]

At the moment I'm experiencing an issue with https and angular proxy: since it seems locked/limited in angular and unrelated to this specific issue here, I ignore it (*) by omitting the first https url from applicationUrl in launchSettings.json and I proceed with the test of this PR.

(*) I will open a different issue for this maybe, just in case it will be needed... I read that you recently introduced this new proxy approach... I don't know why it doesn't work for me (or, well, I guess it doesn't accept the redirect to https without a valid certificate), so, again, I detour it for now, but I remain perplexed, not only about the https proxy, but also about the landing page, the fact that aspnet core redirects to a new ng serve process... Opening the starting app URL in another tab in the browser triggers another ng serve? That sounds wrong.