Changelog History
Page 2
-
v2.0.0-alpha.5 Changes
March 20, 2020 -
v2.0.0-alpha.4 Changes
March 16, 2020๐ This release of SmokeHTTP provides compatibility with Swift 5.0 and Swift 5.1 using SwiftNIO 2.x.
- Use async-http-client. (#47)
-
v2.0.0-alpha.3 Changes
March 11, 2020๐ This release of SmokeHTTP provides compatibility with Swift 5.0 and Swift 5.1 using SwiftNIO 2.x.
๐ฒ 1. Add a SmokeInvocationTraceContext type for basic logging and tracing. (#45)
-
v2.0.0-alpha.2 Changes
March 07, 2020Dependency fix.
-
v2.0.0-alpha.1 Changes
March 07, 2020 -
v1.1.0 Changes
October 13, 2019โ Add the ability to choose if the server will shutdown on a received signal. Retains the default behaviour of shutting down on a SIGINT signal, adding an option to shutdown on SIGTERM and to ignore all signals.
-
v1.0.0 Changes
April 04, 2019๐ This release of SmokeHTTP provides compatibility with Swift 4.1 and Swift 4.2 using SwiftNIO 1.x.
-
v0.9.0 Changes
April 04, 2019๐ Improve the state mutation of SmokeHTTP1Server and to shut down the server when the surrounding application is closing. Provide the ability to execute closures when the server is shutdown.
Note: This is a breaking change -
SmokeHTTP1Server.startAsOperationServer()
will no longer block until the server shuts down.SmokeHTTP1Server.waitUntilShutdown*()
will need to be called to block a thread until the server is shut down. -
v0.8.0 Changes
February 05, 2019- [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.
- The operation input can now conform 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 withStandardSmokeHTTP1HandlerSelector
now need to specify their input and output location in the request or response. - 0๏ธโฃ The default operation delegate is now specified in the initialiser of
StandardSmokeHTTP1HandlerSelector
rather than in theSmokeHTTP1Server.startAsOperationServer
.
- [HTTP1] provides the ability to construct operation input and output types from or to more than just the request and response body.
-
v0.7.0 Changes
November 01, 20180๏ธโฃ Restructures HTTP1-specific operation types into a separate library to allow SmokeOperations to be protocol-agnostic. Also adds an invocation strategy that by default hands off each request to DispatchQueue.global(). This avoids running operations on the thread from SwiftNIO and running into issues with the event loop. Provides an extension point with a strategy protocol if required.
Note: This is a breaking change. The package import for HTTP1-specific operation types will need to change from SmokeOperations to SmokeOperationsHTTP1.