mirror of
https://github.com/nushell/nushell.git
synced 2025-08-10 14:28:11 +02:00
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
This commit is contained in:
@ -84,7 +84,7 @@ pub enum PipelineDataHeader {
|
||||
///
|
||||
/// Items are sent via [`StreamData`]
|
||||
ListStream(ListStreamInfo),
|
||||
/// Initiate [`nu_protocol::PipelineData::ByteStream`].
|
||||
/// Initiate [`nu_protocol::PipelineData::byte_stream`].
|
||||
///
|
||||
/// Items are sent via [`StreamData`]
|
||||
ByteStream(ByteStreamInfo),
|
||||
@ -650,11 +650,11 @@ impl<D> EngineCallResponse<D> {
|
||||
impl EngineCallResponse<PipelineData> {
|
||||
/// Build an [`EngineCallResponse::PipelineData`] from a [`Value`]
|
||||
pub fn value(value: Value) -> EngineCallResponse<PipelineData> {
|
||||
EngineCallResponse::PipelineData(PipelineData::Value(value, None))
|
||||
EngineCallResponse::PipelineData(PipelineData::value(value, None))
|
||||
}
|
||||
|
||||
/// An [`EngineCallResponse::PipelineData`] with [`PipelineData::Empty`]
|
||||
/// An [`EngineCallResponse::PipelineData`] with [`PipelineData::empty()`]
|
||||
pub const fn empty() -> EngineCallResponse<PipelineData> {
|
||||
EngineCallResponse::PipelineData(PipelineData::Empty)
|
||||
EngineCallResponse::PipelineData(PipelineData::empty())
|
||||
}
|
||||
}
|
||||
|
Reference in New Issue
Block a user