Move Weather page to the Blazor Web Client project when using WebAssembly-based interactivity#55877
Move Weather page to the Blazor Web Client project when using WebAssembly-based interactivity#55877mkArtakMSFT wants to merge 3 commits intomainfrom
Conversation
* Don't generate the weather forecast API when either: * Auto mode is used * We're generating an empty template * Removed extra whitespace * Reorganized/refactored the weather forecast model and service * Fixed issues with weather forecast files being included when they shouldn't be
|
This PR currently updates the templates so that when WebAssembly is the only enabled interactive render mode, the This has some limitations:
We could alternatively:
While it solves the issues I described above, it does introduce a tad bit more complexity into the template. However, it's closer to what I believe we'd recommend for a real, production-quality app. An even better long term solution would be to utilize #51584 when it gets implemented, but that may happen after the template changes for .NET 9 have been locked down. Thoughts? |
|
cc @dotnet/aspnet-blazor-eng |
Addresses #55307