Dobromir Nikolov

Perfect! I've updated the Optional.Async package, noting that it's deprecated.

I just tried migrating some of our services to using Optional 5.0, but ran into the following missing extensions: ``` SomeWhenAsync SomeWhenAsync SomeNotNullAsync SomeNotNullAsync ``` We also use `FilterAsync`, which...

@silkfire That's the nature of open source. I've been using my own [Optional.Async](https://github.com/dnikolovv/optional-async) library for quite a while now. It's not extensively maintained but it gets the job done.

@seanhess Glad you managed to resolve the issue! The documentation is indeed lacking. Can you open an issue in https://github.com/eir-forsakring/aws-lambda-haskell-runtime-wai?

I get it. We haven't had a use case for that yet, but I'll make a note to implement HTTP API support.

@shmish111 502 usually means you aren't reaching the lambda at all. It's not a problem with the runtime, it's probably a misconfig.

Just notifying you guys that I'm working on that. Should be shipped with v4.0.0 that has no TH. Update: This is done in https://github.com/theam/aws-lambda-haskell-runtime/pull/97

Hey, I'm not sure whether this should be done. Does the newer way of setting up lambdas not work for your usecase? It's simpler now, you don't need to construct...

Is this helpful? https://theam.github.io/aws-lambda-haskell-runtime/02-adding-a-handler.html This + the next section is how you define and then register a handler.

Yes, it's now deprecated. I guess you can try pinning to the version that works for you?