Nabil Abdel-Hafeez
Nabil Abdel-Hafeez
@nau @guizmaii There are two reasons. 1. We want to be independent of Netty. Not only for JS/Native, but also to be able to offer different backends in the JVM....
@jdegoes This problem is not solvable in a clean way in zio-http. We need to fix this in zio-schema. 1. The Scala 3 macro behaves different then the Scala 2...
@jdegoes please check again
@jdegoes this PR has mainly microservice architecture in mind. But I am not sure about the header forwarding. This solution uses fiber refs, but it could be as well using...
I understand the goal of using the same codec at two places. And it is a good use case. I think the first thing I'd change about how to approach...
@decoursin There is no intention and will never be to support non schema based codecs directly in zio-https Endpoint API. The Endpoint API _is schema based_. But, we use under...
@decoursin why do you want to derive the json codec in the first place? Why not just use the default schema based json codec? Also, yes using a non schema...
> To me it's bewildering that I can't seamlessly use zio-json encoding/decoding with zio HTTP. I can even do with that Tapir. > > But I don't mean to disrespect...
the goal should be, that there is no need for non schema based codecs in almost all cases
> `zio-json` is turing complete. `zio-schema` is not turing complete. There is no limits what I can do with `zio-json`, that's not the case for `zio-schema`. This is not true....