☂️ · partysync

[threepointone]

• schema driven configuration: use zod or valibot or something so folks don't have to deal with raw records
• migrations: how?
• can we hold only a section of data in memory? by date? or some other index?
• eventually, we'd like to use the real WAL to sync data
• what's the recommendation for wiping out deleted records tho? I suppose some time-based expiry should work.
• how should anything that calls onAction() directly trigger a broadcast?

[aulneau]

schema driven configuration: use zod or valibot or something so folks don't have to deal with raw records
migrations: how?

drizzle?

[threepointone]

/oc summarize

[opencode-agent]

Issue Summary: ☂️ · partysync

This is an umbrella issue tracking the development roadmap for partysync - an experimental state synchronization package in the PartyServer monorepo.

Current Status

The partysync package exists in packages/partysync/ and is marked as experimental. This issue tracks several planned improvements and open questions.

Tracked Items

Item	Description	Status
Schema-driven configuration	Use Zod, Valibot, or similar for type-safe schemas instead of raw records	Open
Migrations	How to handle schema/data migrations	Open
Partial data in memory	Hold only a section of data (by date or other index) rather than full dataset	Open
Real WAL sync	Eventually use the real Write-Ahead Log for data synchronization	Open
Deleted record cleanup	Recommendation for wiping deleted records - time-based expiry suggested	Open
onAction() broadcast	How should direct onAction() calls trigger broadcasts	Open

Community Discussion

A community member (@aulneau) suggested using Drizzle as a potential solution for both schema-driven configuration and migrations, given its TypeScript-first approach and built-in migration support.

Key Open Questions

1. What schema library to adopt (Zod, Valibot, Drizzle, etc.)?
2. How to implement migrations in a Durable Objects context?
3. What indexing strategy for partial data loading?
4. What's the right TTL/expiry strategy for soft-deleted records?

This is a planning/tracking issue with no code changes requested.

opencode session  |  github run

[clearlysid]

The more widely adopted standard is probably zod, which is where my vote would go. The migrations are an interesting conundrum. Ideally migrations should be a "user space" problem, and I'm not sure enforcing an ORM/ish tool is the best for that.