Example declaration files
Understand the three small JSON fixtures included with SaveTether and what their review should show.
On this page
The SaveTether package includes three JSON fixtures under SaveTether/Examples/. They are declaration and manifest documents for testing comparisons; they are not game save files and do not contain real player data. The website links the same sample files from the test recipe.
| File | Purpose | Expected result |
|---|---|---|
Previous.json |
Earlier release manifest with persistent identities A, B, and C. | Supplies the baseline for comparison. |
CurrentValid.json |
Current declarations with A, B, and D persistent, C → D as an explicit proposal, and a non-persistent Transient record. |
A and B are conserved, C is removed, D is added; the explicit mapping is accepted and Transient is excluded. |
CurrentWithCycle.json |
Same current declarations, with proposals A → B and B → A. | The cycle is rejected; the proposal does not alter any save data. |
Use copies in a disposable test project and an empty output folder. The expected results validate SaveTether’s declared-identity review only; they do not test a game’s serializer, loader, or migration code. See declare persistent identities and mapping rules.