Struct LiveTeam 

pub struct LiveTeam {
    pub members: Vec<Live>,
    pub poll_seconds: i64,
    pub stale_after_seconds: i64,
}

What the team is doing right now: GET /api/v1/team/live.

Its own endpoint rather than a field on /team/days, because the two are asked at completely different rates. The week’s hours are a page load; the pulse is a poll every half minute, and answering it with the week’s totals would make the dashboard re-run the heaviest query on the server on a timer

• for numbers that did not change.

Keyed by user id so the caller merges it into the table it already drew. Nothing here identifies a person beyond that id: the row a manager may see was decided by /team/days, and this endpoint applies the same clause rather than a second reading of it.

Fields

members: Vec<Live>

poll_seconds: i64

How often the caller should ask again, in seconds. The server owns the cadence - it is the side that knows the staleness threshold.

stale_after_seconds: i64

After how many seconds of silence a pulse stops being believed, so the UI can explain “offline” with the same number the server used.

Trait Implementations

impl Debug for LiveTeam

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

Formats the value using the given formatter.

impl Serialize for LiveTeam

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

where __S: Serializer,

Serialize this value into the given Serde serializer.