Skip to content

For HTTP1, provide the ability to construct operation input and output from more than just the request and response body

Choose a tag to compare

View all tags
@tachyonics tachyonics released this 05 Feb 18:42
0.8.0
15842dd
  • [HTTP1] provides the ability to construct operation input and output types from or to more than just the request and response body.
    • The operation input can now conform to OperationHTTP1InputProtocol to specify how the input type is constructed from the HTTP1 request. The operation input type can be constructed from the request headers, body, query string and url path tokens.
    • The operation output can now conform to OperationHTTP1OutputProtocol to specify how the HTTP1 response is constructed from the output type. The operation output type can specify the response headers and body.
    • The operation input and output types can still conform to Codable but when being registered must specify the location in the request and response they correspond to.
  • [HTTP1] Handler selection using StandardSmokeHTTP1HandlerSelector can now take into account tokens in the url path.

Note: This is a breaking change.

  • Handlers with Codable input and output registered with StandardSmokeHTTP1HandlerSelector now need to specify their input and output location in the request or response.
  • The default operation delegate is now specified in the initialiser of StandardSmokeHTTP1HandlerSelector rather than in the SmokeHTTP1Server.startAsOperationServer.
Assets 2
Loading