Massimo Costa

thanks for the reply, maybe a note in documentation might help

Hello, I'd like start contributing to the project and I found this marked as `help wanted`. Is it still something you wanna implement with help ?

No, I'm wondering if a default implementation could have the same feature than the HTTP one. ============== Massimo Costa Il mer 29 giu 2022, 18:51 Peter Bourgon ***@***.***> ha scritto:...

Something like > Go kit provides default implementation for many functions (for instance `http.EncodeJSONResponse`, `nats.EncodeJSONResponse`, `http.DefaultErrorEncoder`, `nats.DefaultErrorEncoder`,...) but is designed to allow consumers to provide their implementation (maybe to use...

> Neat! So I haven't fully explored this yet, but I think the entire endpoint layer might be able to go away with generics — the transport layer should be...

> Isn't it more natural to do data validation at the service layer? I think there is no objective reason for the endpoint layer to exist. It only steals work...

> is the phone number in the correct format? is the provided transfer amount greater than zero? etc. — which should occur at the service layer. At transport layer you...

> The transport layer should not check semantic validity, because semantic validity is a property of, or defined by, or 1-to-1 with, the service itself. Whereas schema and protocol validity...

Agree, better to stay wrapper agnostic. I like the idea to expose a `*sql. Db` instead of `Tx`: it will make easier use some wrapper if needed. The rationale of...

Can you suggest "where" to put this sentence in the documentation? - website - README file - ... ?