Struct HistoryReply

pub struct HistoryReply {
    pub history: Vec<HistoryEntry>,
    pub status: ReplyStatus,
    pub error: Option<Box<ReplyError>>,
}

Fields

history: Vec<HistoryEntry>

status: ReplyStatus

error: Option<Box<ReplyError>>

Implementations

impl HistoryReply

pub fn as_child_of(&self, parent: &JupyterMessage) -> JupyterMessage

Create a new JupyterMessage, assigning the parent for a HistoryReply message.

This method creates a new JupyterMessage with the right content, parent header, and zmq identities, making it suitable for sending over ZeroMQ.

Example

use jupyter_protocol::messaging::{JupyterMessage, JupyterMessageContent};

let message = connection.recv().await?;

let child_message = HistoryReply{
  // ...
}.as_child_of(&message);

connection.send(child_message).await?;

impl HistoryReply

pub fn new(history: Vec<HistoryEntry>) -> Self

Trait Implementations

impl Clone for HistoryReply

fn clone(&self) -> HistoryReply

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for HistoryReply

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for HistoryReply

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl From<HistoryReply> for JupyterMessage

fn from(content: HistoryReply) -> Self

Create a new JupyterMessage for a HistoryReply.

⚠️ If you use this method, you must set the zmq identities yourself. If you have a message that “caused” your message to be sent, use that message with as_child_of instead.

impl From<HistoryReply> for JupyterMessageContent

fn from(content: HistoryReply) -> Self

Create a new JupyterMessageContent for a HistoryReply.

impl Serialize for HistoryReply

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.