inkandswitch / inkandswitch/tiny-essay-editor

How do migrations work?

Open
#68 0 comments 1 reaction 0 assignees View on GitHub
Dominant language
TypeScript
Stars
260
Forks
30
PR merge metrics
No merged PRs in 30d

Description

I've been reading the [automerge doc section](https://automerge.org/docs/cookbook/modeling-data/#versioning) on migrations, and frankly it's a bit terrifying. As the (AFAICT) largest repo using of automerge, how do you guys handle changing the schema?

The simplest approach (with a single authoritative server serving both code and data) I can imagine is disallowing sync after a code update until the client has migrated it's local data to match the single sync server's version. Is something like that easy to do with automerge?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.