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

History

Johannes Millan d0b7bda01a fix(sync): heal missing idle config field on schema-migration upgrade (#9124 ) A v18.14 snapshot (schema v2) lacks globalConfig.idle.isSuppressIdleDuring FocusMode, which #8965 added as a required field without its own schema bump. Upgrading bumps the snapshot onto the v2->v4 migration path, whose validation gate — uniquely, the only validator that runs on the RAW snapshot before the loadAllData reducer can backfill defaults, and the only one that is fatal rather than repair-or-tolerate — rejects it. Hydration then aborts, recovery refuses because a snapshot still exists, and the app boots to an empty store, deterministically, every launch. Two fixes: - v2->v3 migration backfills the opt-in default (false) when the field is not already a boolean (never clobbering a real user choice), so the migrated snapshot validates and a clean v4 snapshot persists immediately. - The migration-path state-validation gate is now non-fatal: on failure it rolls the on-disk cache back to the pre-migration backup (never persisting an unvalidated snapshot) but returns the migrated snapshot for reducer-healed hydration, instead of throwing into disaster recovery. Genuinely corrupt state is still caught at Checkpoint C and not persisted. Metadata-validation failures remain fatal. Both paths are sabotage-tested to fail without their fix. A known follow-up (noted in code) can persist a fresh snapshot after any migration-then-valid hydration so the safety-net path converges in one boot instead of re-migrating each launch for a not-yet-backfilled field.		2026-07-17 18:35:49 +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): heal missing idle config field on schema-migration upgrade (#9124 )	2026-07-17 18:35:49 +02:00
super-sync-server	fix(supersync): make interrupted CONCURRENTLY migrations recoverable	2026-07-17 17:56:57 +02:00
sync-core	fix(sync): keep import author in client-side clock pruning (#9096 ) (#9102 )	2026-07-17 12:35:15 +02:00
sync-providers	fix(sync): defer LocalFile folder pick commit to settings Save (#9075 ) (#9085 )	2026-07-16 19:11:02 +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

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