Łukasz Lampart

Hi, I have recently picked up the idea of generating documentation. Tried to utilize [docless](https://github.com/timeoutdigital/docless) because it is written purely in scala, not dependent on reflection-based swagger java. Unfortunately it...

Recently i picked up some resolve to tackle this issue after discovering that [this library](https://github.com/AVSystem/scala-commons/blob/master/docs/REST.md) provide almost full coverage of OpenApi specification. Unfortunately it is not separate from the of...

Hello, Regarding response code encoding, i think it is hard to do it properly. What we can do i think is abstract away `Result[A]` and leave it for the specific...

On the side note, i think that all this type noise is not necessary when it comes down to executor, it does only need to know that Endpoint accepts hlist...

Regarding migration to scala 3.0, I think it should be relatively easy to migrate all of chimney functionality to scala 3, checkout my pet project: https://github.com/wookievx/domain-slices. While usage is different...

Regarding my previous comment, given how much of the actual chimney code are macros (90% or more), it is probably a good idea to re-implement entire model from scratch, I...

Thank you for your input. There are some features missing from chimney in scala 3. I am hoping to address some of that during holidays. Regarding cross-compilation, it is tricky...

I created a few github issues in my fork (missing/different features, improvements to implementation). Chimney is surprisingly complicated library requiring to specify and implement: - how to handle compilation errors...

I am working on new way of derivation in my spare time, current state is here: https://github.com/wookievx/chimney/pull/2, Right now I am working on making the tests pass and to implement...

We had very similar issue at my workplace that old consumer kept consuming after being revoked. From what I gathered from the linked issue and rebalance listener implementation all the...