Open kamilkloch opened 9 months ago
Do you see where the problem is? I guess it would be high time to add some tests for the pipeToBody
specifically
Accumutor is always None
- lines https://github.com/softwaremill/tapir/blob/fdfa3da9a7d96b49625412a3aebed3ffe4e87988/server/http4s-server/src/main/scala/sttp/tapir/server/http4s/Http4sWebSockets.scala#L76 through https://github.com/softwaremill/tapir/blob/fdfa3da9a7d96b49625412a3aebed3ffe4e87988/server/http4s-server/src/main/scala/sttp/tapir/server/http4s/Http4sWebSockets.scala#L79 are never invoked.
Question, if such functionality is actually needed. http4s concatenates web socket frames by default, not sure about the other servers.
It is, not all servers do :) Though of course, can't tell right now which don't ;) I just remember this being the case ...
But, astonishingly, nobody is complaining about non-concatenating the frames by tapir interpreter for other servers.
Yes, maybe these are unpopular servers, or people don't send fragmented frames that often. I don't know really :)
Current implementation of
optionallyConcatenateFrames
returns the original stream:https://github.com/softwaremill/tapir/blob/fdfa3da9a7d96b49625412a3aebed3ffe4e87988/server/http4s-server/src/main/scala/sttp/tapir/server/http4s/Http4sWebSockets.scala#L71