Components
Signature cards and editor
Define a personal or inbox-specific email signature in a consistent editing surface.
On this page
Purpose and composition
Define a personal or inbox-specific email signature in a consistent editing surface.
Keep signature configuration separate from recipient identity.
Anatomy
| Part | Responsibility |
|---|---|
| Card | Name, owner, scope and default status |
| Editor | Name, owner, usage scope and body |
| Default | Native checkbox |
Configuration and variants
| Input / variant | Contract |
|---|---|
| signature | Optional sample object |
| onClose/onSave | No-argument callbacks |
| submit gate | Name and body nonblank |
| scope | All inboxes or source inbox names |
States and feedback
| State | Visible / behavioral result |
|---|---|
| Default | Explicit label |
| New/edit | Draft initialized from sample |
| Invalid | Submit disabled |
Interaction and responsive behavior
- Body is plain textarea content.
- Name and body are required; owner and scope select source labels.
- Save closes with toast in source parent.
Accessibility contract
- Visible field labels name controls.
- Default checkbox is native.
Known implementation limits
No actual signature append/delivery or persistent edit is wired; callbacks do not receive the draft fields.
Composition example
<SignatureEditor signature={sample} onClose={close} onSave={notifyLocal} />Source references
| File | Responsibility |
|---|---|
| components/views/settings-view.tsx | Signature sample cards |
| components/views/settings-editors.tsx | SignatureEditor |
Examples from the app
Actual Sonarist components with fictional conversations, people, example.com addresses and simulated operational states. Captured at 2× resolution or higher. Select an image to inspect it full size.
Related topics
Source audit: 2026-10-08 · Revision 10f45d1377b5 · Documentation v1.0.0