Expand description
What a client and this server exchange.
Both enums are tagged on kind, which is added beside a messageβs own
fields rather than replacing anything, so a reader can tell what a
message is without knowing its shape. The tag is the contract:
adding a variant is compatible and renaming one is not.
Re-exportsΒ§
use forge_primitives::document::DocumentKind;πuse forge_primitives::git_diff::LayerState;πuse forge_primitives::ClientConfig;πuse forge_primitives::SessionSlot;πuse forge_workspace::DictateAxes;πuse forge_workspace::env::git_diff::content::FileContent;πuse serde::Deserialize;πuse serde::Deserialize;πuse serde::Serialize;πuse serde::Serialize;πuse super::wire::ReviewedThreadWire;πuse crate::live::fleet_news;πuse crate::Command;πuse crate::SessionUpdate;π
StructsΒ§
- Browser
File Wire - One chosen file on the wire: its name and its bytes, base64.
- Client
Settings - What the client draws with, from
forge.tomlby way of the server. - Seat
Frame Wire - One repaired frame: the number the seat minted for it, and the update
itself in the same shape a live
updatecarries.
EnumsΒ§
- Client
Message - What a client sends.
- Server
Message - What the server sends.
- Settings
Refusal - Why a settings save was refused.
- Subject
- What a client can watch. A subscription names one of these and is answered with that subjectβs snapshot.
FunctionsΒ§
- board_
detail π - The updates whose whole effect is the boardβs own snapshot.
- seat_
liveness π - The seat events a board rowβs
stalemark is read from.