Domantas Petrauskas

Same issue happens with `dependencyTree`.

I guess having an effectful client provider is also a way to go, but still a question about first-class support in endpoint4s remains.

Or we could just add a new value to `EndpointSettings`, which would be used for resolution instead of `baseUri` if provided. That would take care of backwards compatibility.

Feels like adding a `EndpointSettings` parameter `baseUrlLookup: () => Future[String]` would open up most capabilities with the least effort. You can do resolution each call or caching then. Failed call...

Since browser clients cannot interact with upgrade response/request, I though it would be best to explicitly separate `webSocket` and `webSocketWithUpgrade`. My thinking was that if an endpoint describes an interaction...

After doing more research and thinking, I do not think that a stream is a correct abstraction to express data flowing through a WebSocket. Issue with streams is that they...

@nadavwr I mainly focused on reducing the amount of redundant dependencies, which was mainly caused by transient dependencies - project had many modules depending on a lot of code that...

It is somewhat tricky - I think we want to preserve default behavior of keeping the port in familiar range of `8000-8009`, but also allow passing `0`. Problem here comes...

Not sure, @evanw could you comment on this issue? Need your confirmation before exploring solutions.

Could the size of the offline puzzle buffer be configurable through settings? Some constant number is bound to eventually not suit some users.