Îõ³h$Fÿ(C) 2021 Bellroy Pty Ltd BSD-3-Clause'Bellroy Tech Team  experimentalNone ÑÔÙàìówai-handler-halConvert a WAI + into a function that can be run by hal's Å. This is the simplest form, and probably all that you'll need. See ! if you have more complex needs.wai-handler-halConvert a WAI + into a function that can be run by hal's 4. This function exposes all the configurable knobs.wai-handler-halâConvert the request sent to a Lambda serving an API Gateway proxy integration into a WAI request.Note:Í We aren't told the HTTP version the client is using, so we assume HTTP 1.1.wai-handler-halConvert a WAI  into a hal .wai-handler-halÖVault of values to share between the application and any middleware. You can pass in Data.Vault.Lazy., or  if you don't want to depend on vault directly.wai-handler-hal‰API Gateway doesn't tell us the port it's listening on, so you have to tell it yourself. This is almost always going to be 443 (HTTPS).wai-handler-hal We pass two  ) keys to the callback that provides the 0. This allows the application to look into the   part of each request and read hal data structures, if necessary:The    á provides information about the Lambda invocation, function, and execution environment; andThe   (   )É provides the unmodified API Gateway representation of the HTTP request.wai-handler-hal We force   because it's a type alias for à (i.e., should always parse), and it avoids an "ambiguous type variable" error at the use site.    .wai-handler-hal-0.1.2.0-BXUpi4O9nx2AC9mlzlNj2RNetwork.Wai.Handler.HalAWS.Lambda.RuntimemRuntimemRuntimeWithContext' Data.AesonValuerunrunWithContext toWaiRequestfromWaiResponse wai-3.2.3-BLrwfdFdeMQ1KnKjrnSyUl Network.Wai ApplicationNetwork.Wai.InternalResponse hal-1.0.0-KslKQhHo8gE94B5KS6DGiq*AWS.Lambda.Events.ApiGateway.ProxyResponse ProxyResponse$vault-0.3.1.5-3uSXZUrpSDM33ZOYfxNkG8Data.Vault.LazyemptybaseGHC.BasememptyVaultKeyAWS.Lambda.Context LambdaContext)AWS.Lambda.Events.ApiGateway.ProxyRequest ProxyRequest NoAuthorizer