ProtectedconstructorCreate an Adapter.
The blueprint to create the adapter.
Protected ReadonlyblueprintProtected ReadonlyhooksProtected ReadonlymiddlewareProtected ReadonlyresolvedProtectedbuildBuild the raw response.
The event context.
OptionaleventHandler: AdapterEventHandlerType<IncomingHttpEvent, OutgoingHttpResponse>
The event handler to be run.
The raw response wrapper.
ProtectedeventHandle a single Azure HttpRequest, producing an HttpResponseInit.
The incoming request.
The Azure invocation context.
The response init.
ProtectedexecuteExecute the event handler lifecycle hooks.
The hook to execute.
The event handler to be run.
ProtectedexecuteExecute adapter lifecycle hooks.
The hook's name.
Optionalcontext: AzureFunctionsHttpAdapterContext
The event context.
Optionalerror: any
The error to handle.
ProtectedhandleHandle error.
The error to handle.
The event context.
The raw response.
ProtectedhandleHandle the event.
The event context.
The event handler to be run.
The raw response wrapper.
ProtectedmakeCreate pipeline options for the Adapter.
The pipeline options for transforming the event.
ProtectedonLifecycle hook run once before the first request.
ProtectedresolveGet the error handler for the given error.
The error to get the handler for.
The error handler.
ProtectedresolveStart the adapter and return the Azure Functions HTTP handler.
The Azure Functions HTTP handler.
ProtectedsendSend the raw event through the destination.
The event context.
The event handler to be run.
Platform-specific response.
ProtectedvalidateValidate the context and event handler.
The context to validate.
The event handler to validate.
StaticcreateThe application blueprint.
A new adapter instance.
Azure Functions v4 HTTP adapter for Stone.js.
Azure Functions v4 invokes an HTTP-triggered function with a Web-standard
HttpRequestand expects anHttpResponseInitback. Unlike a server adapter,run()does not start a listener — it returns the handler(request, invocationContext) => Promise<HttpResponseInit>that you register withapp.http('name', { handler })from@azure/functions.Because the request is Web-standard, the normalizer is the same one the Fetch adapter uses; only the raw response differs (an
HttpResponseInitobject rather than aResponse).Example