Expand description
Typed HTTP client for the Edda services. Shared by every frontend so none of them need to know about URLs, headers or status codes.
Modules§
- admin
- Client for the services’ admin API (see
edda_server::admin), for whoever runs them, such as a hosting’s control plane: creating campaigns and their DMs’ setup codes, exporting a whole campaign to keep or move elsewhere and importing it there, and deleting campaigns. - auth
- Client for the auth service: setting up devices and logging in.
- combat
- Client for the combat service: HTTP access, a live WebSocket connection
and
Replica, which gives frontends instant (predicted) feedback. - monsters
- Client for the monster service: monsters, and the full text of spells and conditions.
- pairing
- Pairing devices with a short code: the DM’s device (“host”) and a new
device (“joiner”) run the PAKE in
edda_auth::pairing, relayed by the auth service.
Structs§
- Client
- The character service’s client.
Enums§
- Client
Error - What can go wrong talking to a service.