group streaming related changes

Author: Bahex

blog/2025-10-14-nushell_v0_108_0.md

@@ -388,17 +388,6 @@ Error: nu::shell::cant_convert
 00000010 00000001
 ```
 
-### `for` loops no longer collect their source ([#16593])
-Previously, `for` loops only worked with values (ranges, lists, etc), so using them with streaming commands would collect the whole stream before iteration could start. Now it also works with streams too! 
-
-This makes it possible to use it with slow or unbounded streams:
-
-```nushell
-for event in (watch . --glob=**/*.rs) {
-	cargo test
-}
-```
-
 ### Guess no more! More completions in built-in commands ([#16383])
 
 Thanks to some recent improvements behind the scenes, nushell built-in commands that expect a specific set of values now suggests these values.
@@ -533,6 +522,117 @@ def fish-completer [spans: list<string>] {
 
 </details>
 
+### `for` loops no longer collect their source ([#16593])
+Previously, `for` loops only worked with values (ranges, lists, etc), so using them with streaming commands would collect the whole stream before iteration could start. Now it also works with streams too! 
+
+This makes it possible to use it with slow or unbounded streams:
+
+```nushell
+for event in (watch . --glob=**/*.rs) {
+	cargo test
+}
+```
+
+### Streams of Streams ([#16735])
+
+When you run `each` over a list (or stream), it can only return a single item for each input. When we need to create multiple values from a single input, we can just return a list in the closure and run the output through `flatten`.
+
+```nushell
+each { .. } | flatten
+```
+
+When the closure itself generates a _stream_ however, that pattern can be inadequate, as the stream has to be collected into a list, just to be flattened afterwards. This might increase memory usage, and result in unnecessary waits.
+
+To address this, `each` has a new flag: `--flatten`
+
+`each --flatten` does not wait to collect closure output to ensure returning a single output item for each input, instead the stream from the closure is directly passed through. Here's a demonstration of differences:
+
+<table>
+<tbody>
+<tr>
+<td>
+
+```nushell:title="each | flatten"
+def slow-source [range: range] {
+    $range | each {|e| sleep 0.1sec; $e }
+}
+
+0..5..<25
+| each {|e| slow-source ($e)..<($e + 5) }
+| flatten
+| each {|e| print $e; $e}
+| ignore
+```
+
+</td>
+<td>
+
+```nushell:title="each --flatten"
+#
+def slow-source [range: range] {
+    $range | each {|e| sleep 0.1sec; $e }
+}
+
+0..5..<25
+| each --flatten {|e| slow-source ($e)..<($e + 5) }
+| each {|e| print $e; $e}
+| ignore
+```
+
+</td>
+</tr>
+<tr>
+<td width="50%">
+
+![each then flatten](https://gist.githubusercontent.com/Bahex/50beec0aaf82671d55f23feda65dca27/raw/690cdbe49d761d8a8f0886451868cd16fe275184/pr_16735_old.nu.cast.svg)
+
+</td>
+<td width="50%">
+
+![each --flatten](https://gist.githubusercontent.com/Bahex/50beec0aaf82671d55f23feda65dca27/raw/690cdbe49d761d8a8f0886451868cd16fe275184/pr_16735_new.nu.cast.svg)
+
+</td>
+</tr>
+</tbody>
+</table>
+
+### Arbitrary Pipeline Metadata ([#16821])
+
+In addition to existing metadata fields (`content_type`, `source`, `span`), it's now possible to attach arbitrary metadata fields to pipeline data using `metadata set --merge`:
+
+```nushell
+"data" | metadata set --merge {custom_key: "value"} | metadata | get custom_key
+```
+
+Combined with `metadata access`, this makes it possible to carry extra data with streams, without impacting the stream data itself.
+
+### HTTP Response Metadata ([#16821])
+
+All `http` commands now attach response data (previously only accessible with `http * --full`) as metadata to their output streams. This can be accessed under the `http_response` field within the pipeline metadata:
+
+- `status` - HTTP status code
+- `headers` - Response headers as `[{name, value}, ...]`
+- `urls` - Redirect history
+
+Accessing this metadata after the response completes may not offer much benefit.
+```nushell
+http get https://api.example.com | metadata | get http_response.status
+# => 200
+```
+
+Where it shines is accessing it _alongside_ the streaming response body using `metadata access`:
+```nushell
+http get --allow-errors https://api.example.com/events.jsonl
+| metadata access {|meta|
+    if $meta.http_response.status != 200 {
+        error make {msg: "failed"}
+    } else { }
+  }
+| lines
+| each { from json }
+| where event_type == "error"
+```
+
 ### Add `$nu.is-lsp` to help with printing in lsp mode ([#16635])
 When nushell is launched with the `--lsp` flag, nushell will set `$nu.is-lsp` to true so that users can programmatically know when nushell is in LSP mode.
 
@@ -708,69 +808,6 @@ The `str length` command now has a `--chars` flag to allow you to count characte
   5
 ```
 
-### Streams of Streams ([#16735])
-
-When you run `each` over a list (or stream), it can only return a single item for each input. When we need to create multiple values from a single input, we can just return a list in the closure and run the output through `flatten`.
-
-```nushell
-each { .. } | flatten
-```
-
-When the closure itself generates a _stream_ however, that pattern can be inadequate, as the stream has to be collected into a list, just to be flattened afterwards. This might increase memory usage, and result in unnecessary waits.
-
-To address this, `each` has a new flag: `--flatten`
-
-`each --flatten` does not wait to collect closure output to ensure returning a single output item for each input, instead the stream from the closure is directly passed through. Here's a demonstration of differences:
-
-<table>
-<tbody>
-<tr>
-<td>
-
-```nushell:title="each | flatten"
-def slow-source [range: range] {
-    $range | each {|e| sleep 0.1sec; $e }
-}
-
-0..5..<25
-| each {|e| slow-source ($e)..<($e + 5) }
-| flatten
-| each {|e| print $e; $e}
-| ignore
-```
-
-</td>
-<td>
-
-```nushell:title="each --flatten"
-#
-def slow-source [range: range] {
-    $range | each {|e| sleep 0.1sec; $e }
-}
-
-0..5..<25
-| each --flatten {|e| slow-source ($e)..<($e + 5) }
-| each {|e| print $e; $e}
-| ignore
-```
-
-</td>
-</tr>
-<tr>
-<td width="50%">
-
-![each then flatten](https://gist.githubusercontent.com/Bahex/50beec0aaf82671d55f23feda65dca27/raw/690cdbe49d761d8a8f0886451868cd16fe275184/pr_16735_old.nu.cast.svg)
-
-</td>
-<td width="50%">
-
-![each --flatten](https://gist.githubusercontent.com/Bahex/50beec0aaf82671d55f23feda65dca27/raw/690cdbe49d761d8a8f0886451868cd16fe275184/pr_16735_new.nu.cast.svg)
-
-</td>
-</tr>
-</tbody>
-</table>
-
 ### The `to md` command now always returns valid Markdown tables ([#16681])
 Previously, a command like this:
 ```shell
@@ -797,45 +834,6 @@ Now, such special characters are automatically escaped, ensuring the output alwa
 ### `compact` your records ([#16810])
 `compact` can now be used to remove `null` or `--empty` items from records too.
 
-### `compact --empty` now recognizes 0 byte binary values as empty ([#16810])
-
-### Arbitrary Pipeline Metadata ([#16821])
-
-In addition to existing metadata fields (`content_type`, `source`, `span`), it's now possible to attach arbitrary metadata fields to pipeline data using `metadata set --merge`:
-
-```nushell
-"data" | metadata set --merge {custom_key: "value"} | metadata | get custom_key
-```
-
-Combined with `metadata access`, this makes it possible to carry extra data with streams, without impacting the stream data itself.
-
-### HTTP Response Metadata ([#16821])
-
-All `http` commands now attach response data (previously only accessible with `http * --full`) as metadata to their output streams. This can be accessed under the `http_response` field within the pipeline metadata:
-
-- `status` - HTTP status code
-- `headers` - Response headers as `[{name, value}, ...]`
-- `urls` - Redirect history
-
-Accessing this metadata after the response completes may not offer much benefit.
-```nushell
-http get https://api.example.com | metadata | get http_response.status
-# => 200
-```
-
-Where it shines is accessing it _alongside_ the streaming response body using `metadata access`:
-```nushell
-http get --allow-errors https://api.example.com/events.jsonl
-| metadata access {|meta|
-    if $meta.http_response.status != 200 {
-        error make {msg: "failed"}
-    } else { }
-  }
-| lines
-| each { from json }
-| where event_type == "error"
-```
-
 ### Breaking changes
 
 ### `collect` removes `source` metadata ([#16821])
@@ -1042,6 +1040,8 @@ This was due to a miscompilation bug, which is now fixed.
 
 ### Other fixes
 
+* `compact --empty` now recognizes 0 byte binary values as empty ([#16810])
+
 * Fixed associative equality comparison for floats. ([#16549])
 
 * The `**` (power) operator now parses as right-associative instead of left-associative, matching standard mathematical behavior. ([#16552])