How blaxbb/ghapitest works
This is a small Blazor WebAssembly client paired with an ASP.NET Core weather API. The visible API workflow registers and dispatches controller routes; its GET handler generates forecast records, while its POST handler echoes a submitted location. The client entry point mounts the root component and configures an HttpClient, but the supplied excerpts do not show page routing or API requests. The README is empty, and unsampled page behavior and client/server wiring are therefore not inferred.
Main entry points: WeatherForecastController.cs Forecast controller · Blazor/Program.cs Client host · WebAPI/Program.cs API host · App.razor App root
Components 12
Blazor client
- Client host
Blazor/Program.cs - App root
Blazor/App.razor - Home page
Blazor/Pages/Home.razor - Weather page
Blazor/Pages/Weather.razor - Counter page
Blazor/Pages/Counter.razor - Not found page
Blazor/Pages/NotFound.razor - Main layout
Blazor/Layout/MainLayout.razor - Navigation menu
Blazor/Layout/NavMenu.razor
Weather API
- API host
WebAPI/Program.cs - Forecast controller
WebAPI/Controllers/WeatherForecastController.cs - Forecast model
WebAPI/WeatherForecast.cs
Other components
- Browser user
Connections 3
- Client host → App root: mounts
Blazor/Program.cs - API host → Forecast controller: maps routes
WebAPI/Program.cs - Forecast controller → Forecast model: creates records
WebAPI/Controllers/WeatherForecastController.cs