pub struct ContractRenderData {Show 22 fields
pub kind: String,
pub kind_label: String,
pub number: String,
pub subtitle: Option<String>,
pub effective_date_display: String,
pub end_date_display: Option<String>,
pub term_text: String,
pub term_short: String,
pub governing_law: String,
pub jurisdiction_phrase: String,
pub venue: Option<String>,
pub status: String,
pub draft_watermark: bool,
pub fee_text: Option<String>,
pub fee_short: Option<String>,
pub our_party: PartyData,
pub their_party: PartyData,
pub parties_prose: Vec<String>,
pub clauses: Vec<ClauseRenderData>,
pub signature: SignatureBlock,
pub logo: Option<String>,
pub internal_notes: Option<String>,
}Fields§
§kind: String§kind_label: StringFormal document type — the title of the page (e.g. “Consulting Services Agreement”, “Mutual Non-Disclosure Agreement”). This is what real contracts put at the top, not the kind tag from the CLI.
number: StringInternal reference code (CTR-…, NDA-…). Rendered only in the page footer at small size for filing purposes — never on the body.
subtitle: Option<String>User-supplied contract title (e.g. project name). Rendered as a
subtitle UNDER the formal kind-label only when the user gave a
meaningful title (i.e. not the auto-generated “Kind — A × B”).
None suppresses the subtitle entirely.
effective_date_display: StringEffective date in display format (“24 May 2026”). Used in the “DATED” line above the parties section.
end_date_display: Option<String>§term_text: String§term_short: StringCompact term phrase for the key-terms strip (“2 months”, “until 1 Jul 2026”).
governing_law: String§jurisdiction_phrase: String§venue: Option<String>§status: String§draft_watermark: bool§fee_text: Option<String>§fee_short: Option<String>Compact fee phrase for the key-terms strip (“£1,500 fixed”).
our_party: PartyData§their_party: PartyData§parties_prose: Vec<String>Parties as numbered prose lines, the traditional UK contract format: “BORIS DJORDJEVIC of 199 Gloucester Terrace, London W2 6LD, United Kingdom (the "Consultant")” Templates render them as a numbered list “(1) … ; and (2) ….”.
clauses: Vec<ClauseRenderData>§signature: SignatureBlock§logo: Option<String>§internal_notes: Option<String>Trait Implementations§
Source§impl Debug for ContractRenderData
impl Debug for ContractRenderData
Auto Trait Implementations§
impl Freeze for ContractRenderData
impl RefUnwindSafe for ContractRenderData
impl Send for ContractRenderData
impl Sync for ContractRenderData
impl Unpin for ContractRenderData
impl UnsafeUnpin for ContractRenderData
impl UnwindSafe for ContractRenderData
Blanket Implementations§
Source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
Source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Source§impl<T> Paint for Twhere
T: ?Sized,
impl<T> Paint for Twhere
T: ?Sized,
Source§fn fg(&self, value: Color) -> Painted<&T>
fn fg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self with the foreground set to
value.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like red() and
green(), which have the same functionality but are
pithier.
§Example
Set foreground color to white using fg():
use yansi::{Paint, Color};
painted.fg(Color::White);Set foreground color to white using white().
use yansi::Paint;
painted.white();Source§fn bright_black(&self) -> Painted<&T>
fn bright_black(&self) -> Painted<&T>
Source§fn bright_red(&self) -> Painted<&T>
fn bright_red(&self) -> Painted<&T>
Source§fn bright_green(&self) -> Painted<&T>
fn bright_green(&self) -> Painted<&T>
Source§fn bright_yellow(&self) -> Painted<&T>
fn bright_yellow(&self) -> Painted<&T>
Source§fn bright_blue(&self) -> Painted<&T>
fn bright_blue(&self) -> Painted<&T>
Source§fn bright_magenta(&self) -> Painted<&T>
fn bright_magenta(&self) -> Painted<&T>
Source§fn bright_cyan(&self) -> Painted<&T>
fn bright_cyan(&self) -> Painted<&T>
Source§fn bright_white(&self) -> Painted<&T>
fn bright_white(&self) -> Painted<&T>
Source§fn bg(&self, value: Color) -> Painted<&T>
fn bg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self with the background set to
value.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like on_red() and
on_green(), which have the same functionality but
are pithier.
§Example
Set background color to red using fg():
use yansi::{Paint, Color};
painted.bg(Color::Red);Set background color to red using on_red().
use yansi::Paint;
painted.on_red();Source§fn on_primary(&self) -> Painted<&T>
fn on_primary(&self) -> Painted<&T>
Source§fn on_magenta(&self) -> Painted<&T>
fn on_magenta(&self) -> Painted<&T>
Source§fn on_bright_black(&self) -> Painted<&T>
fn on_bright_black(&self) -> Painted<&T>
Source§fn on_bright_red(&self) -> Painted<&T>
fn on_bright_red(&self) -> Painted<&T>
Source§fn on_bright_green(&self) -> Painted<&T>
fn on_bright_green(&self) -> Painted<&T>
Source§fn on_bright_yellow(&self) -> Painted<&T>
fn on_bright_yellow(&self) -> Painted<&T>
Source§fn on_bright_blue(&self) -> Painted<&T>
fn on_bright_blue(&self) -> Painted<&T>
Source§fn on_bright_magenta(&self) -> Painted<&T>
fn on_bright_magenta(&self) -> Painted<&T>
Source§fn on_bright_cyan(&self) -> Painted<&T>
fn on_bright_cyan(&self) -> Painted<&T>
Source§fn on_bright_white(&self) -> Painted<&T>
fn on_bright_white(&self) -> Painted<&T>
Source§fn attr(&self, value: Attribute) -> Painted<&T>
fn attr(&self, value: Attribute) -> Painted<&T>
Enables the styling Attribute value.
This method should be used rarely. Instead, prefer to use
attribute-specific builder methods like bold() and
underline(), which have the same functionality
but are pithier.
§Example
Make text bold using attr():
use yansi::{Paint, Attribute};
painted.attr(Attribute::Bold);Make text bold using using bold().
use yansi::Paint;
painted.bold();Source§fn rapid_blink(&self) -> Painted<&T>
fn rapid_blink(&self) -> Painted<&T>
Source§fn quirk(&self, value: Quirk) -> Painted<&T>
fn quirk(&self, value: Quirk) -> Painted<&T>
Enables the yansi Quirk value.
This method should be used rarely. Instead, prefer to use quirk-specific
builder methods like mask() and
wrap(), which have the same functionality but are
pithier.
§Example
Enable wrapping using .quirk():
use yansi::{Paint, Quirk};
painted.quirk(Quirk::Wrap);Enable wrapping using wrap().
use yansi::Paint;
painted.wrap();Source§fn clear(&self) -> Painted<&T>
👎Deprecated since 1.0.1: renamed to resetting() due to conflicts with Vec::clear().
The clear() method will be removed in a future release.
fn clear(&self) -> Painted<&T>
renamed to resetting() due to conflicts with Vec::clear().
The clear() method will be removed in a future release.
Source§fn whenever(&self, value: Condition) -> Painted<&T>
fn whenever(&self, value: Condition) -> Painted<&T>
Conditionally enable styling based on whether the Condition value
applies. Replaces any previous condition.
See the crate level docs for more details.
§Example
Enable styling painted only when both stdout and stderr are TTYs:
use yansi::{Paint, Condition};
painted.red().on_yellow().whenever(Condition::STDOUTERR_ARE_TTY);