Release 1.0.3

Author: adamw

README.md

@@ -21,13 +21,13 @@ preserving developer-friendly stack traces, and without compromising performance
 To use Ox, add the following dependency, using either [sbt](https://www.scala-sbt.org):
 
 ```scala
-"com.softwaremill.ox" %% "core" % "1.0.2"
+"com.softwaremill.ox" %% "core" % "1.0.3"
 ```
 
 Or [scala-cli](https://scala-cli.virtuslab.org):
 
 ```scala
-//> using dep "com.softwaremill.ox::core:1.0.2"
+//> using dep "com.softwaremill.ox::core:1.0.3"
 ```
 
 Documentation is available at [https://ox.softwaremill.com](https://ox.softwaremill.com), ScalaDocs can be browsed at [https://javadoc.io](https://www.javadoc.io/doc/com.softwaremill.ox).

generated-doc/out/index.md

@@ -2,7 +2,7 @@
 
 Safe direct-style streaming, concurrency and resiliency for Scala on the JVM. Requires JDK 21+ & Scala 3.
 
-To start using Ox, add the `com.softwaremill.ox::core:1.0.2` [dependency](info/dependency.md) to your project. 
+To start using Ox, add the `com.softwaremill.ox::core:1.0.3` [dependency](info/dependency.md) to your project. 
 Then, take a look at the tour of Ox, or follow one of the topics listed in the menu to get to know Ox's API!
 
 In addition to this documentation, ScalaDocs can be browsed at [https://javadoc.io](https://www.javadoc.io/doc/com.softwaremill.ox).

generated-doc/out/info/dependency.md

@@ -4,10 +4,10 @@ To use ox core in your project, add:
 
 ```scala
 // sbt dependency
-"com.softwaremill.ox" %% "core" % "1.0.2"
+"com.softwaremill.ox" %% "core" % "1.0.3"
 
 // scala-cli dependency
-//> using dep com.softwaremill.ox::core:1.0.2
+//> using dep com.softwaremill.ox::core:1.0.3
 ```
 
 Ox core depends only on the Java [jox](https://github.com/softwaremill/jox) project, where channels are implemented. There are no other direct or transitive dependencies.

generated-doc/out/integrations/cron4s.md

@@ -3,7 +3,7 @@
 Dependency:
 
 ```scala
-"com.softwaremill.ox" %% "cron" % "1.0.2"
+"com.softwaremill.ox" %% "cron" % "1.0.3"
 ```
 
 This module allows to run schedules based on cron expressions from [cron4s](https://github.com/alonsodomin/cron4s).

generated-doc/out/integrations/kafka.md

@@ -3,7 +3,7 @@
 Dependency:
 
 ```scala
-"com.softwaremill.ox" %% "kafka" % "1.0.2"
+"com.softwaremill.ox" %% "kafka" % "1.0.3"
 ```
 
 `Flow`s which read from a Kafka topic, mapping stages and drains which publish to Kafka topics are available through

generated-doc/out/integrations/mdc-logback.md

@@ -3,7 +3,7 @@
 Dependency:
 
 ```scala
-"com.softwaremill.ox" %% "mdc-logback" % "1.0.2"
+"com.softwaremill.ox" %% "mdc-logback" % "1.0.3"
 ```
 
 Ox provides support for setting inheritable MDC (mapped diagnostic context) values, when using the [Logback](https://logback.qos.ch)

generated-doc/out/integrations/otel-context.md

@@ -3,7 +3,7 @@
 Dependency:
 
 ```scala
-"com.softwaremill.ox" %% "otel-context" % "1.0.2"
+"com.softwaremill.ox" %% "otel-context" % "1.0.3"
 ```
 
 When using the default OpenTelemetry context-propagation mechanisms, which rely on thread-local storage, the context

generated-doc/out/streaming/flows.md

@@ -60,6 +60,26 @@ As part of the callback, you can create [supervision scopes](../structured-concu
 
 Any asynchronous communication should be best done with [channels](channels.md). You can then manually forward any elements received from a channel to `emit`, or use e.g. `FlowEmit.channelToEmit`.
 
+Alternatively, flows can be created by providing a function that receives a `Sink` (channel):
+
+```scala
+import ox.flow.Flow
+import ox.{fork, supervised}
+
+supervised:
+  Flow.usingChannel: sink =>
+    sink.send(1)
+    fork:
+      sink.send(2)
+      sink.send(3)
+    sink.send(4)
+  // TODO: transform the flow further & run
+```
+
+Unlike `usingEmit`, the `Sink` instance can be safely shared across threads, as channels are thread-safe. The provided function is run asynchronously in a forked task. The flow completes when the function completes and the sink is automatically closed. If the function throws an exception, it is propagated as a flow error.
+
+Note that `Flow.usingChannel` must be run within a concurrency scope, as it creates a fork to run the provided function.
+
 ## Transforming flows: basics
 
 Multiple transformation stages can be added to a flow, each time returning a new `Flow` instance, describing the extended pipeline. As before, no elements are emitted or transformed until the flow is run, as flows are lazy. There's a number of pre-defined transformation stages, many of them similar in function to corresponding methods on Scala's collections:
@@ -171,7 +191,7 @@ To obtain a `org.reactivestreams.Publisher` instance, you'll need to add the fol
 bring the `toReactiveStreamsPublisher` method into scope:
 
 ```scala
-// sbt dependency: "com.softwaremill.ox" %% "flow-reactive-streams" % "1.0.2"
+// sbt dependency: "com.softwaremill.ox" %% "flow-reactive-streams" % "1.0.3"
 
 import ox.supervised
 import ox.flow.Flow