TimelineItem
TimelineItem is the event record used by Timeline.
Each item represents one moment or milestone in a sequence, such as an activity log entry, message event, deployment step, or support history item.
Example
use fission::prelude::*;
let item = TimelineItem {
title: "Build finished".into(),
description: Some("All checks passed on main.".into()),
timestamp: Some("10:24".into()),
};
Field table
Field | Type | Meaning | Notes / default behavior |
|---|---|---|---|
title | String | Main event label. | Required. |
description | Option<String> | Supporting explanation below the title. | Defaults to None. |
timestamp | Option<String> | Optional time or date label. | Defaults to None. Format it upstream. |
Specific advice
Keep timestamps human-readable and consistent across items. A timeline becomes harder to scan if each item uses a different date or time format.
Production checklist
For TimelineItem, review the fields that change behavior before treating the widget as finished: title, description, timestamp. The goal is to make the product rule visible in state and actions, not hidden inside ad-hoc construction code.
•
If this widget appears inside an interactive flow, keep the surrounding action binding in the parent component and test that the flow still has one clear reducer path.
•
Check the semantics tree for the user-facing label or role that makes this widget understandable without relying only on pixels.
•
Add at least one component or harness test that confirms the visible text, semantic role, action dispatch, and layout constraint that matter for this widget in context.
If a screen starts repeating the same TimelineItem setup, extract a named component around this widget. That keeps the reference API small while making product code easier to read and safer for generated code to copy.