Nikolai Kudasov

@23Skidoo Nice, we'll of course add a CI configuration to build TH version too! We'll try to prepare a PR next week.

@nikita-volkov @Unisay we have been using our fork which is linked in this discussion and can be found at https://github.com/GetShopTV/ekg/pull/1. We've been using it with Stack as follows: ```yaml -...

@klappvisor I'm currently experimenting with Telegram Bot API using this library. This was the first thing I noticed. However it is a very minor thing. Recently I noticed that Telegram...

This might have to do with either - having a huge unifying `TelegramBotAPI` type (and deriving client for that); - having a lot of `Generic`-based deriving for large record types....

@cdupont I know I'm late, but see https://github.com/haskell-servant/servant-swagger/issues/45#issuecomment-219148710 (in a nutshell, you just need [`simpleCors`](https://hackage.haskell.org/package/wai-cors-0.2.4/docs/Network-Wai-Middleware-Cors.html#v:simpleCors) middleware).

@sordina if someone were to use `cors` from `wai-cors` together with `provideOptions` from `servant-options`, then one would override the other, right?

@sordina ok, I must be missing something, but it seems to me that `cors` overrides responses for `OPTIONS` completely, rendering `provideOptions` effectless. No?

I think there was an issue somewhere (can't find it now) to add combinator(s) that'd use `ToForm`/`FromForm` to parse `FormURLEncoded` request bodies and/or `QueryParam`s. I think that would be more...

@3noch I agree with @dmjio. Unfortunately `DataKinds` can't yet lift any (even constant) terms to the type level. Besides, I don't like defaults parameter values *on the handler side*. If...

@3noch if you're a client of such API then I guess you can treat any `QueryParam` with default value as `RequiredQueryParam` and always pass values explicitly. No need to encode...