Skip to content

Test that version history survives schema changes #652

Description

@jamiefolsom

Before anything reads the stored record objects back (a draft-then-publish workflow will), verify version history against schema changes: on a model that has version records, add and remove fields, then confirm nothing breaks. Write down what handling a stored version needs once its schema is out of date.

Today the stored object isn't read anywhere, so this is expected to pass — the point is to know before we build on it.

Related: #639, #640.

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions