Expand description
Core types for pidge: accounts, configuration, and the normalized message model.
This crate is intentionally provider-agnostic — it knows nothing about HTTP,
Microsoft Graph, or authentication. Those concerns live in pidge-client.
Structs§
- Account
- A signed-in Microsoft account.
- Attachment
- An attachment listed on a message. Bytes are NOT included — fetch separately
via
GraphClient::get_attachment_bytes(account, message_id, attachment.id). - Cached
Message Ref - Config
- Defaults
- Full
Message - Full message content as returned by
GraphClient::get_message. Compared toMessage(the list-row shape), this carries full body, all recipient lists, sent/received timestamps, and ahas_attachmentsflag for triggering the attachment fetch. - Message
- One message in a mailbox, as presented to commands and output formatters.
- Message
Cache - Message
From
Enums§
- Body
Content Type - Cache
Lookup - Result of looking up a fragment against the cache.
- Core
Error - Flag
Status - Outlook’s follow-up flag state on a message. Three values to match what
Graph returns; the CLI currently only sets
Flagged/NotFlagged, but it reads and displays all three so a flag a user completed in Outlook shows up correctly here. - Token
Storage - Where pidge stores OAuth tokens for an account.
Functions§
- short_
hash - Compute the 8-char hex short hash for a Graph ID. Deterministic: same input -> same output. Stable across pidge runs and machines.