Krzysztof Ciesielski

@kamilkloch Yes, we'd like to add it as well. The Netty server is now undergoing some config enhancements (with https://github.com/softwaremill/tapir/issues/3056 still pending) and I think that adding WS support will...

The problem is that `read` and `write` methods are defined in the `Api` trait of uPickle, so we need an object which extends `upickle.Api`, and this object is our `TapirPickle`....

Here are some notes after my initial analysis: ### General remarks Some of our requirements can be addressed with the `@upickle.implicits.key` annotation. I don't know if we can add annotations...

I see, thanks for explaining with enumerations, let's use the terminology as you suggested. The discussion board you posted looks promising. I was able to find a [fresh thread on...

Leaving some notes after our recent discussion with @adamw: 1. The main API entrypoint is `Pickler`, and we want to allow deriving picklers without users providing schemas. 2. If we...

Hi @decoursin, thank your for submitting the idea. I think Circe uses specific number of arguments, because they don't want to allow unsafe executions. The `list.get(i).get` call can throw an...

BTW how about using `@encodedName`? https://tapir.softwaremill.com/en/latest/endpoint/schemas.html?highlight=encodedName#customising-derived-schemas

@WojciechMazur thanks a lot for this contribution! > org.typesafe.scalalogging is available only for JVM, it's usage on Scala.js and Scala Native would fail at link-time. PR contains a workaround allowing...

@WojciechMazur Could you take a look at my questions?

@jumale could you change the issue title to reflect that it's about adding a new module?