mirror of https://github.com/johannesjo/super-productivity.git synced 2026-07-25 08:53:50 +00:00

History

Johannes Millan 43c10ed73b refactor(sync): polish storage delta tracking and update tests Picked up the remaining items from the multi-agent review: - Hoist Operation / ServerOperation imports in sync.routes.ts so the upload path no longer needs `as unknown as import('./sync.types').*` double casts. The Set + filter pattern for accepted ops becomes an index-zip loop, dropping two iterations + the Set allocation. - Pull APPROX_BYTES_PER_OP out of two inline locals in sync.service.ts into sync.const.ts so the constant is a single source of truth and the trade-off (over-estimate vs observed median op size) is documented in one place. - Log when computeOpsStorageBytes silently skips an op whose payload fails JSON.stringify (BigInt, circular refs). Counter still under-counts but the cause is visible in logs. - Update storage-quota docstrings to reflect that calculateStorageUsage / updateStorageUsage are now legitimately called from the freeStorageForUpload reconcile path (rare cleanup events), not only offline. Tests: - cleanup.spec.ts: assert updateStorageUsage is NOT called after deleteOldSyncedOpsForAllUsers (the per-user SUM loop was the DoS). - storage-quota-cleanup.spec.ts: drop the assertion that deleteOldestRestorePointAndOps issues a pg_column_size query (it does not anymore); add a $executeRaw mock that mutates testUsers so the iterative-cleanup test exercises the real decrement path; tune starting storage to within a few KB of quota so cleanup's approximate decrement can detect progress within a few iterations. - storage-quota.service.spec.ts: add the $executeRaw prisma mock and unit tests for incrementStorageUsage / decrementStorageUsage (positive path, Math.floor of non-integer deltas, no-op on NaN/Infinity/zero/negative, clamped UPDATE for decrement).		2026-05-12 16:46:38 +02:00
..
plugin-api	build(plugin-api): stop tracking generated source map	2026-05-11 14:38:52 +02:00
plugin-dev	fix(oauth): disable insecure Google Calendar web flow	2026-05-09 18:14:38 +02:00
shared-schema	refactor(sync): move vector clocks to sync-core	2026-05-11 15:21:08 +02:00
super-sync-server	refactor(sync): polish storage delta tracking and update tests	2026-05-12 16:46:38 +02:00
sync-core	refactor(sync): address extraction review findings	2026-05-12 12:52:39 +02:00
vite-plugin	chore(deps): bump the npm_and_yarn group across 1 directory with 9 updates (#7259 )	2026-04-18 20:35:50 +02:00
build-packages.js	refactor(sync): move vector clocks to sync-core	2026-05-11 15:21:08 +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