Pepe García

Hi @SemanticBeeng Yep, I think hammock is a good idea if you're planning to cross-compile here. Regarding the imports in the macro, currently most of mu is defaulting to Http4s...

>In the long run , in the spirit of "Clients should remain Scala.js compatible" #21, mu development will consider having separate macros for generating scala.js compatible clients. yep, that's possible....

Yes, even though we have some documentation in http://pepegar.com/hammock/docs, I think we should add more to express more real use cases.

Hey Devon! sorry for the late response... Decoding an entity to a case class via circe can be done with the `hammock-circe` module. You can see an example here https://scastie.scala-lang.org/F5wqP0yNRTiDQPa73lQL4w...

Currently I don't have a lot of time to put into OSS. However, I'd be more than happy to help if you want to contribute the websockets module in hammock...

The real problematic part is node. Do you use the library in browser apps or in node apps?

Hi @rlecomte! Yeah, you're right that receiving it as a constructor param and using it in the `transK` method is a bit repetitive. However, since the interface we need to...

Hey @mukel ! Yeah, multipart is something we definitely want to introduce. I think the idea would be to create a new `MultipartEntity`, and map it to the underlying implementations.

CC/ @antonkulaga

Working on it now