gaelic-ghost/socket/build-falco-web-app

Build Falco Web App

Use Falco for its lightweight functional HTTP surface while leaving business behavior as ordinary, testable F# code.

Source Check

Read existing routes, the web host, project references, tests, and configuration before editing. Consult Falco's source and documentation and ASP.NET Core documentation for current package behavior.

Workflow

1. Confirm Falco is the selected framework; otherwise start with

dotnet:choose-fsharp-web-framework.

1. Define route handlers around one request job. Parse input, call a domain

function, then write one explicit response shape.

1. Keep routing declarative and readable. Split route groups by feature instead

of building one mutable registration surface.

1. Use the existing ASP.NET Core host for configuration, dependency registration,

authentication, authorization, logging, and rate or upload limits. Do not hide those platform concerns in unrelated response helpers.

1. Treat HTML/view code as presentation. Keep it separate from request parsing,

authorization, and persistence behavior.

1. Test domain modules without a host, then add endpoint or integration coverage

for routes, input validation, auth decisions, and response contracts.

Validation

Run the repository's targeted commands. If it has none, use:

dotnet build <web-project.fsproj>
dotnet test <test-project.fsproj>

Boundaries

• Preserve F# compile order and explicit task or async boundaries.
• Do not translate C# controller or service patterns mechanically into Falco.
• For Azure resources, hosting, monitoring, identity, or deployment, use the

official Azure Skills handoff rather than inventing provider commands here.