Wayfinder.Engine.Http
0.1.0
dotnet add package Wayfinder.Engine.Http --version 0.1.0
NuGet\Install-Package Wayfinder.Engine.Http -Version 0.1.0
<PackageReference Include="Wayfinder.Engine.Http" Version="0.1.0" />
<PackageVersion Include="Wayfinder.Engine.Http" Version="0.1.0" />
<PackageReference Include="Wayfinder.Engine.Http" />
paket add Wayfinder.Engine.Http --version 0.1.0
#r "nuget: Wayfinder.Engine.Http, 0.1.0"
#:package Wayfinder.Engine.Http@0.1.0
#addin nuget:?package=Wayfinder.Engine.Http&version=0.1.0
#tool nuget:?package=Wayfinder.Engine.Http&version=0.1.0
Wayfinder.Engine.Http
The engine's own HTTP-request-processing glue a host otherwise hand-copies per route. Plain
functions, no routing of its own — a host calls these from inside its own minimal-API handlers,
the same way Wayfinder.Rendering.GovUk's GovUkStageJourney
functions are called (see that package's own README for the sibling functions this one pairs
with — posted-form field coercion, file-download URL injection).
Why a separate package from Wayfinder.Rendering.GovUk
Wayfinder.Rendering.GovUk deliberately has no dependency on Wayfinder.Engine — it only ever
touches Wayfinder.Models.ServiceDesign types plus its own rendering functions. File-upload
handling genuinely needs IServiceRequestFileStorage (Wayfinder.Engine.Abstractions), so it
lives here instead, keeping that dependency boundary honest rather than pulling the whole engine
into a package that otherwise works from any HTTP host.
Usage
var problems = await StageFileUploads.ApplyFileUploadsAsync(
form, envelope.Render, instanceId, fileStorage, fieldValues);
Validates every file-upload field on the current stage against its own declared
MaxSizeBytes/AcceptedFileTypes, saves an accepted file via IServiceRequestFileStorage, and
writes the resulting ServiceRequestFileReference into fieldValues. A field with no file posted
this time round is left untouched entirely, so the engine's own merge preserves whatever reference
(if any) the instance already has stored. Returns one ServiceRequestProblem per rejected file —
empty means every posted file was accepted, or none were posted at all.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- Wayfinder.Engine (>= 0.7.0)
NuGet packages (2)
Showing the top 2 NuGet packages that depend on Wayfinder.Engine.Http:
| Package | Downloads |
|---|---|
|
Wayfinder.Engine.Worklist
A default, optional caseworker worklist surface — server-rendered GOV.UK markup for the filter/sort/search/paginated list (see docs/guides/queue-worklist-filtering.md), an item review page, advance, and per-cursor pickup/putback (see docs/guides/work-allocation.md). A host wires it up with AddWorklist()/MapWorklist(prefix), supplying only tenant/actor resolution and its own page chrome — or ignores this package entirely and hand-writes the same routes itself, as Wayfinder.ReferenceApp originally did. |
|
|
Wayfinder.Engine.Journey
A default, optional single-actor journey surface — server-rendered GOV.UK markup for "get my current stage, advance it" against one blueprint (the applicant/citizen shape, as opposed to Wayfinder.Engine.Worklist's multi-item caseworker queue). A host wires it up with AddJourney()/MapJourney(prefix, blueprintKey, pageTitle) — once per blueprint it wants a self-service journey for — or ignores this package entirely and hand-writes the same routes itself. |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 0.1.0 | 76 | 8/19/2026 |