React SPA template is cumbersome to use when adding new API routes due to the proxy requirement

[Eilon]

In the React SPA template there is a file setupProxy.js that seems to control which client HTTP requests get routed to ASP.NET Core (or not):

https://github.com/dotnet/spa-templates/blob/main/src/content/React-CSharp/ClientApp/src/setupProxy.js#L8-L16

I found it a bit cumbersome to have to edit that file when I added new APIs. I ended up grouping all my APIs into /api so that I could just add one entry:

const context = [
    "/weatherforecast",
    "/api",
];

Would it make sense to have some common prefix such as /api so that many common scenarios would just work without having to edit this file?

[leastprivilege]

I personally think that the /weatherforcast route would be sufficient for all my future API requirements.

[Eilon]

Well, yes, weatherforecast stands for "WEb Api Total Holistic Extremely Realistic Full Omnipotent Really Easy Completely Awesome Superb Technology". Thus, all APIs should go under that prefix!

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]

Closing, as the SPA templates have been removed from .NET 8 SDK.