Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a weather API call to the Blazor Web App template when global interactivity is enabled with WebAssembly/Auto #51204

Closed
danroth27 opened this issue Oct 7, 2023 · 5 comments
Labels
area-blazor Includes: Blazor, Razor Components enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-templates ✔️ Resolution: Duplicate Resolved as a duplicate of another issue Pillar: Dev Experience Priority:2 Work that is important, but not critical for the release Status: Resolved
Milestone

Comments

@danroth27
Copy link
Member

The earlier Blazor WebAssembly template demonstrated in the weather page how to make an API call from the client to the server. The new Blazor Web App template no longer demonstrates this scenario - instead the weather page manufactures the weather forecast data in the weather component implementation. It would be instructive if the weather page instead made an API call to the server to get the weather forecast data. This would also provide an opportunity to show how to handle component state persistence when prerendering.

@dotnet-issue-labeler dotnet-issue-labeler bot added the area-blazor Includes: Blazor, Razor Components label Oct 7, 2023
@mkArtakMSFT mkArtakMSFT added enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-templates labels Oct 9, 2023
@mkArtakMSFT mkArtakMSFT added this to the .NET 9 Planning milestone Oct 9, 2023
@ghost
Copy link

ghost commented Oct 9, 2023

Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

@ghost
Copy link

ghost commented Dec 21, 2023

Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

@ghost
Copy link

ghost commented Mar 1, 2024

Could at least describe how to add API to Blazor template in .NET 8????

@danroth27
Copy link
Member Author

Could at least describe how to add API to Blazor template in .NET 8????

@aleksanderwercis You can find docs on calling web APIs from Blazor here: https://learn.microsoft.com/aspnet/core/blazor/call-web-api. If that doesn't answer all your questions, please let us know!

@mkArtakMSFT mkArtakMSFT modified the milestones: .NET 10 Planning, Backlog Nov 1, 2024
@mkArtakMSFT
Copy link
Member

Closing as a dupe of #55307

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-blazor Includes: Blazor, Razor Components enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-templates ✔️ Resolution: Duplicate Resolved as a duplicate of another issue Pillar: Dev Experience Priority:2 Work that is important, but not critical for the release Status: Resolved
Projects
None yet
Development

No branches or pull requests

3 participants