softwaremill / softwaremill/tapir
WebSocket `concatenateFragmentedFrames` is a no-op
Open
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.5k
- Forks
- 468
- Avg merge
- 5h 37m
- Merged PRs (30d)
- 34
Description
Current implementation of optionallyConcatenateFrames returns the original stream:
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in server/http4s-server/src/main/scala/sttp/tapir/server/http4s/Http4sWebSockets.scala at optionallyConcatenateFrames, as identified by the issue. Trace how concatenateFragmentedFrames is handled in the WebSocket stream and determine the expected behavior for fragmented frames; done means the option no longer returns the original stream unchanged and the behavior is covered by the relevant project tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100