mirror of https://github.com/johannesjo/super-productivity.git synced 2026-07-17 16:37:43 +00:00

History

Johannes Millan 2864a39c85 fix(sync): file-based provider atomicity & conflict UX (#8960 ) (#9004 ) * docs(plugins): add microsoft 365 calendar provider plan * docs(plugins): add microsoft 365 calendar provider plan * docs(ios): plan internal testflight builds * fix(sync): prevent file-based sync data loss Preserve post-snapshot operations and stage remote baselines until durable apply. Use conditional writes and a resumable marker for provider concurrency and legacy migration. Report trustworthy remote timestamps and document transport limits. Refs #8960 * fix(sync): avoid biased conflict recommendations Highlight a side only when its timestamp or known change count is strictly greater, leaving unknown and tied metadata neutral. * test(sync): assert options arg on split-file processRemoteOps The split-file snapshot path now routes post-snapshot ops through _processRemoteOpsWithStartupCleanup, which calls processRemoteOps with an (empty) options object. Update the assertion to match the 2-arg call so the unit suite passes. * refactor(sync): dedupe strong-ETag regex, document snapshot-op boundary - Extract the duplicated RFC 7232 strong-entity-tag pattern into a single STRONG_ETAG_RE constant with a comment noting why the char class is safe to interpolate into an If-Match header (no CR/LF header splitting). - Explain why sv === undefined ops are classified as snapshot-included: they are legacy migration ops fully contained in the snapshot, and _validateSnapshotRef enforces a clock-EQUAL boundary. No behavior change.		2026-07-14 19:23:24 +02:00
..
plugin-api	feat(plugin): add PluginAPI.request with manifest allowedHosts allowlist (#8721 )	2026-07-07 11:50:17 +02:00
plugin-dev	fix(plugins): prevent automation rule data loss (#8972 )	2026-07-13 19:12:13 +02:00
shared-schema	fix(sync): preserve multi-entity conflict recovery (#8990 )	2026-07-14 14:10:52 +02:00
super-sync-server	fix(sync): preserve multi-entity conflict recovery (#8990 )	2026-07-14 14:10:52 +02:00
sync-core	fix(sync): preserve multi-entity conflict recovery (#8990 )	2026-07-14 14:10:52 +02:00
sync-providers	fix(sync): file-based provider atomicity & conflict UX (#8960 ) (#9004 )	2026-07-14 19:23:24 +02:00
vite-plugin	chore(deps): bump esbuild in the npm_and_yarn group across 0 directory (#8451 )	2026-06-17 14:41:32 +02:00
build-packages.js	fix(plugin): refresh procrastination buster i18n #5102 (#8145 )	2026-06-08 20:44:43 +02:00
README.md	feat: cleanup and update plugins 2	2025-06-29 06:36:02 +02:00

README.md

Super Productivity Packages

This directory contains plugin packages and the plugin API for Super Productivity.

Structure

plugin-api/ - TypeScript definitions for the plugin API
plugin-dev/ - Plugin development examples and tools
- api-test-plugin/ - Basic API test plugin
- procrastination-buster/ - Example SolidJS-based plugin
- yesterday-tasks-plugin/ - Simple plugin showing yesterday's tasks
- boilerplate-solid-js/ - Template for creating new SolidJS plugins (not built)
- sync-md/ - Markdown sync plugin (not built)

Building Packages

All packages are built automatically when running the main build process:

npm run build:packages

This command:

Builds the plugin-api TypeScript definitions
Builds plugins that require compilation (e.g., procrastination-buster)
Copies plugin files to src/assets/ for inclusion in the app

Development

To work on a specific plugin:

cd plugin-dev/[plugin-name]
npm install
npm run dev

Adding a New Plugin

Create a new directory in plugin-dev/
Add the plugin configuration to /packages/build-packages.js
Run npm run build:packages to test the build

Notes

The boilerplate-solid-js and sync-md plugins are development templates and are not included in production builds
Plugin files are automatically copied to src/assets/ during the build process
The build script handles dependency installation automatically