Struct ObjectWriter 

pub struct ObjectWriter { /* private fields */ }

What: Builder of one compact JSON object in insertion order, as JSON.stringify writes it. A struct groups named fields; this one holds the text written so far. Why: Records must list their fields in the incumbent’s order so the bytes match for the same values; escaping comes from serde_json, which escapes the same characters JSON.stringify does.

In TS you’d write (pseudocode):

JSON.stringify({ a: 1, b: 'x' })

Implementations

impl ObjectWriter

Methods that append one field each and finish the object.

pub fn new() -> Self

What: Start an empty object. Why: Every record starts the same way.

In TS you’d write (pseudocode):

const record = {};

pub fn string(&mut self, key: &str, value: &str) -> &mut Self

What: Append a text field. Why: Most record fields are text.

In TS you’d write (pseudocode):

record[key] = value;

pub fn integer(&mut self, key: &str, value: i64) -> &mut Self

What: Append a whole-number field. Why: Schema versions, process IDs and attempt numbers.

In TS you’d write (pseudocode):

record[key] = value;

pub fn boolean(&mut self, key: &str, value: bool) -> &mut Self

What: Append a boolean field. Why: Flags such as whether a prepared commit is signed.

In TS you’d write (pseudocode):

record[key] = value;

pub fn raw(&mut self, key: &str, json: &str) -> &mut Self

What: Append a field whose value is already complete JSON text. Why: Nested objects and arrays are built by their own writers.

In TS you’d write (pseudocode):

record[key] = nested;

pub fn finish(&self) -> String

What: The finished object text. Why: Callers add the record’s line terminator themselves.

In TS you’d write (pseudocode):

JSON.stringify(record)

Trait Implementations

impl Debug for ObjectWriter

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

Formats the value using the given formatter.

impl Default for ObjectWriter

fn default() -> Self

Returns the “default value” for a type.