extern/nushell
1
0
Fork 1
mirror of https://github.com/nushell/nushell.git synced 2025-08-04 01:41:04 +02:00
Code Issues Packages Projects Releases Wiki Activity
Files
eb8d2d32068f02dacd4a28e1b1336bfbcc288a27
nushell/crates/nu-protocol
History
Wind eb8d2d3206 Refactor: introduce 2 associated functions to PipelineData (#16233) 
# Description
As title: this pr is try to introduce 2 functions to `PipelineData`:
1. PipelineData::list_stream --> create a PipelineData::ListStream
2. PipelineData::byte_stream -> create a PipelineData::ByteStream
And use these functions everywhere.

### Reason behind this change
I tried to implement `pipefail` feature, but this would required to
change `PipelineData` from enum to struct. So use these functions can
reduce diff if I finally change to struct. [Discord message
here](https://discord.com/channels/601130461678272522/615962413203718156/1396999539000479784)
is my plan.

# User-Facing Changes
NaN

# Tests + Formatting
NaN

# After Submitting
NaN
2025-08-02 09:30:30 +08:00
..
src
Refactor: introduce 2 associated functions to PipelineData (#16233)
2025-08-02 09:30:30 +08:00
tests
Reapply "refactor(completion, parser): move custom_completion info from Expression to Signature" (#16250) (#16259)
2025-07-25 19:57:00 -04:00
Cargo.toml
Bump version to 0.106.2 (#16295)
2025-07-30 01:36:35 +02:00
LICENSE
Fix rest of license year ranges (#8727)
2023-04-04 09:03:29 +12:00
README.md
Add nu-protocol
2021-09-02 13:29:43 +12:00

README.md

nu-protocol

The nu-protocol crate holds the definitions of structs/traits that are used throughout Nushell. This gives us one way to expose them to many other crates, as well as make these definitions available to each other, without causing mutually recursive dependencies.