How teddyara/blazorstaticwebapptest works
Project type and purpose
• This is a full-stack .NET 8 Blazor WebAssembly application (Client) calling an Azure Functions API (Api), with a shared C# class library (Shared) for common models.
• The README describes it as a starter template: a Blazor WASM client (hosted via Azure Static Web Apps), a Functions-based backend, and shared types.
File structure
• Top-level solution: BlazorStaticWebApps.sln
• “Client” folder: Blazor WASM app, staticwebapp.config.json, wwwroot assets, pages/components/layouts.
• “Api” folder: Azure Functions project (.csproj), BitbucketWebhookFunction.cs, WeatherForecastFunction.cs.
• “Shared” folder: class library for shared DTOs (WeatherForecast.cs, WebhookLogStore.cs).
• Configuration files: host.json, local.settings.json (sample), launchSettings.json, serviceDependencies.json.
• No database folder, but WebhookLogStore suggests a storage abstraction—likely Azure Table/Cosmos/Blob.
README for additional insights
• It instructs how to run locally with Azure Static Web Apps CLI: runs Blazor app on port 5000, Functions on 7071, and swa start proxy on 4280.
• Describes deployments to Azure Static Web Apps.
• Confirms architectural roles: Client ←→ API ←→ Shared.
Detailed breakdown of components
• Frontend (Blazor WASM)
• App.razor, Pages (Home, Counter, FetchData)
• Layouts and NavMenu
• Static files (index.html, CSS, sample-data/weather.json)
• Backend (Azure Functions)
• WeatherForecastFunction (GET endpoint)
• BitbucketWebhookFunction (POST webhook)
• host.json, local.settings.json for config
• Shared (class library)
• WeatherForecast model (DTO)
• WebhookLogStore abstraction (data persistence)
Final advice
• Don’t forget to show how the Shared library ties the two projects together at compile time.