SSaveglint
Workflows

Coding workflows · Game save migrations

03
Built around your work

A concrete starting point

Migrate version-one game saves by adding an inventory field without resetting progress. Test an empty inventory, a damaged save and an unsupported newer version while preserving the original file on failure.

01

Open the context

Choose the project folder and name the files or behavior involved.

02

Define the change

Describe the input, expected output and boundaries that must stay intact.

03

Inspect the work

Review the proposed edits and any commands before relying on their result.

04

Check the outcome

Compare actual behavior with the expected result. If a check fails, investigate it before applying more changes.

Game save migrations

A concrete starting point
function migrate(save: SaveV1): SaveV2 {
  if (save.version !== 1) throw new Error("version");
  return { ...save, version: 2, inventory: [] };
}

The example is a starting point for a real project, not a claim that generated code is already tested. Adjust paths, dependencies and expected behavior to match your application.

AI coding workspace

Your next change starts here.

Get the Windows app ↗