pub enum Reply {
Welcome {
version: Version,
},
Description(Description),
Availability(AvailabilityDecl),
Applies {
applies: bool,
},
Status {
status: Option<String>,
},
LiveChoices {
choices: Vec<ChoiceDecl>,
},
Signals(ReadingDecl),
Done,
Failed {
kind: FailureKind,
detail: String,
},
Ask(Ask),
}Expand description
What an addon says back.
Variants§
Welcome
Answer to Request::Hello.
Description(Description)
Answer to Request::Describe.
Availability(AvailabilityDecl)
Answer to Request::Availability.
Applies
Answer to Request::Applies.
Status
Answer to Request::Status.
LiveChoices
Answer to Request::LiveChoices.
Fields
choices: Vec<ChoiceDecl>In the order the addon wants them shown — the ordering is a concept only the addon has, so the interface renders rather than sorts.
Signals(ReadingDecl)
Answer to Request::ReadSignals.
Done
It worked, and there is nothing to say. Answers Perform, Configure
and Shutdown.
Failed
It did not work.
Fields
kind: FailureKindWhich kind, so the daemon can tell “no such action” from “the target is not running” without parsing prose.
Ask(Ask)
The addon wants one of its own credentials, mid-request.
Not really a reply: the daemon answers with Answer and the addon
then carries on with the request it was already handling. It shares this
channel because there is only one pipe.