fix: Progress Tracking

[Osalotioman]

• Verified that exporting game data currently works.
• Fixed typo reading to => writing to.
• Create default values when json field does not exist for level or world.
• Add a use effect to set code field for levels so they persist in storage.

closes: #489

[joneugster]

Thanks for the PR! I'll have a closer look later

[joneugster]

this is likely correct for when levelId is 0 but I need to check this later

[Osalotioman]

It's not the same behaviour since 0 is falsy, I've updated it so worldProgressAtom does not get updated when we are in level 0.

[joneugster]

Id prefer to use the style export function ... project wide, could you change to that, please? Also, is the as necessary?

[joneugster]

or even better,
this doesn't need to be a create-function does it? This can simply be a constant

const defaultLevelProgress: LevelProgress = {
  ...
}

[Osalotioman]

I've updated it to be a constant, and put it under defaultProgress in progress-atoms.ts.

[joneugster]

Have you consodered if it would make sense that levelProgressAtom directly returns a default, so thos doesn't need to be added in multiple places?

[Osalotioman]

I made levelProgressAtom and worldProgressAtom directly return the defaults, but still ended up adding those defaults in multiple places cause levelProgressAtom is allowed to return null when there is no worldId/progress/levelId/levelProgress. I'm looking through to see if I can take out checks like that so it returns the default value or actual value all the time, then I can remove the default values from other places.

[Osalotioman]

I just noticed a new issue, one that was being blocked earlier cause progress was not being properly updated.
The useEffect in main.tsx which sets the current level as completed when the proof is complete does so pre-maturely when a user takes the following action:

1. User finishes level A, so proof.completed becomes true.
2. User navigates to level B.
3. Before proof state is fully refreshed/reset for level B, that effect can still see the old proof.completed === true.
4. Now the completedAtom auto-creates missing progress, it writes { completed: true } for level B immediately, instead of waiting for proof.completed to get updated when the current proof state finishes loading.

I don't know if I should address it here or leave it for another PR so this one does not go out of scope too much.