tomer doron
tomer doron
@stevapple `context` is needed when users need to initialize resources, it provides thinks like NIO's `EventLoop` and `Terminator`, so we cannot just drop it.
termination is for resource cleanup when shutting down, there needs to be an entry point to that. also all NIO based clients (eg db client based on NIO) need access...
nio's versions are a bit different from the ones in AWSLambdaEvents, the latter are designed for JSON payload decoding/encoding we could consider adding a prefix to more easily disambiguate.
@helje5 IIRC the main issues was that we would need to be extending these types to add functionality to them (Codable conformance mainly IIRC). rule of thumb we have been...
> You don't need to extend the types to decode them (yes, Codable can only be added to the original type itself, but that is not required here). You can...
@eneko you are correct to point out that the deployment examples focus on single-function/single-executable per package users of this library may of course choose to build "larger" packages that include...
@eneko would you like to PR some docs around this so we can close it out? maybe highlighting the tradeoffs and why normally you want to deploy one at a...
> Looking at package manager command plugins, it seems that source code formatting is an example given. > > However, I don't quite understand from that document if this would...
cc @abertelrud the command plugins API has a construct called "intent" in which a plugin author can define the functional goal of the plugin. the idea is that while some...