Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update scalafmt-core to 3.8.4 #468

Closed
wants to merge 3 commits into from
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions .git-blame-ignore-revs
Original file line number Diff line number Diff line change
@@ -1,2 +1,5 @@
# Scala Steward: Reformat with scalafmt 3.8.1
499baded20f959dca86ad7a24d2244b7241de8c3

# Scala Steward: Reformat with scalafmt 3.8.4
55455e7170d23ea63a901f7e9511a934f16d4767
2 changes: 1 addition & 1 deletion .scalafmt.conf
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
runner.dialect = scala213
version = 3.8.3
version = 3.8.4
maxColumn = 120
fileOverride {
"glob:**/scala-3/**" {
Expand Down
4 changes: 2 additions & 2 deletions ws/src/main/scala/sttp/ws/WebSocket.scala
Original file line number Diff line number Diff line change
Expand Up @@ -23,8 +23,8 @@ trait WebSocket[F[_]] {
* happen.
*
* However, not all implementations expose the close frame, and web sockets might also get closed without the proper
* close frame exchange. In such cases, as well as when invoking `receive`/`send` after receiving a close frame, this
* effect will fail with the [[WebSocketClosed]] exception.
* close frame exchange. In such cases, as well as when invoking `receive` /`send` after receiving a close frame,
* this effect will fail with the [[WebSocketClosed]] exception.
*
* *Should be only called sequentially!* (from a single thread/fiber). Because web socket frames might be fragmented,
* calling this method concurrently might result in threads/fibers receiving fragments of the same frame.
Expand Down
Loading