Fixes capabilities implementation package names in the comment

softwaremill · Feb 17, 2025 · 2b243de · 2b243de
1 parent c0e5beb
commit 2b243de
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/client/sttp-client4/src/main/scala/sttp/tapir/client/sttp4/WebSocketToPipe.scala b/client/sttp-client4/src/main/scala/sttp/tapir/client/sttp4/WebSocketToPipe.scala
@@ -4,13 +4,13 @@ import sttp.capabilities.Streams
 import sttp.tapir.WebSocketBodyOutput
 import sttp.ws.WebSocket
 
-/** Captures the logic of converting a [[WebSocket]] to a interpreter-specific pipe, which is then returned to the client. Implementations
+/** Captures the logic of converting a [[WebSocket]] to an interpreter-specific pipe, which is then returned to the client. Implementations
   * of this trait are looked up in the implicit scope by the compiler, depending on the capabilities that are required by the endpoint to be
   * interpreted as a client.
   *
   * For capabilities `R`, where web sockets aren't included, the implementation just throws an unsupported exception (and this logic
   * shouldn't ever be used). For capabilities which include web sockets, appropriate implementations should be imported, e.g. from the
-  * `sttp.tapir.client.sttp.ws.fs2._` or `sttp.tapir.client.sttp.ws.akka._` packages.
+  * `sttp.tapir.client.sttp4.ws.fs2._`, `sttp.tapir.client.sttp4.ws.pekkohttp._` or `sttp.tapir.client.sttp4.ws.zio._` packages.
   */
 trait WebSocketToPipe[-R] {
   type S <: Streams[S]