mirror of
https://github.com/Foundry376/Mailspring.git
synced 2025-03-01 10:33:14 +08:00
cff437e900
* Shfit away from default exports and PropTypes for better TS support * localize strings and expand use of types in WeekView, create new EventOccurence distinct from Event * Remove calendar wrap, use TS enum for view type + consistent prop interface * Bump Typescript to 3.8.3 and improve query / attribute / search typings * Re-use the Autolinker for calendar event descriptions with aggressive phone detection * Clean up WeekView and the editing popover, lots of cruft here * Update ScrollRegion to initialize scrollbar provided by external ref * Expose ScrollRegion’s resizeObserver to clean up tick interval tracking * Simply tickGenerator and move it to a helper * Bump to Electron 8.x for Chrome 75+ CSS features * Bump Handlebars dep to fix annoying npm audit noise * Remove electron-remote from electron-spellchecker * Explicitly add node-gyp, why is this necessary? * Fix lesslint issues * Bump eslint and let it fix 133 issues * Satisfy remaining eslint@2020 errors by hand * Add tsc-watch npm script and fix all TS errors outside calendar * Configure appveyor to publish all the pdb files it gets * Log sync exit codes and signals for easier triage on Windows * Upgrade npm, mark that the build process supports Node 11+ not just Node 11 * Resolve more errors * Upgrade sqlite to be a context-aware native module * Fix: Tab key no longer navigating into contenteditable because tabIndex not inferred * Fix: Bad print styles because Chrome now adds more CSS of it’s own when doctype is missing * Fix: before-navigate is now called after beforeunload |
||
|---|---|---|
| .. | ||
| assets | ||
| lib | ||
| styles | ||
| icon.png | ||
| package.json | ||
| README.md | ||
| screenshot.png | ||
Composer Templates
Create templates you can use to pre-fill the N1 composer - never type the same email again! Templates live in the templates folder inside the Mailspring config folder.
Each template is an HTML file - the name of the file is the name of the template, and it's contents are the default message body.
If you include HTML <code> tags in your template, you can create
regions that you can jump between and fill easily.
Give <code> tags the var class to mark them as template regions. Add
the empty class to make them dark yellow. When you send your message, <code>
tags are always stripped so the recipient never sees any highlighting.
This example is a good starting point for plugins that want to extend the composer experience.
