Component save mechanism

[pietrop]

Describe the bug

At the moment the component uses the url param as a key to save in local storage.
However when you come back to a transcript if it is present in local storage with the current logic that version takes priority over the server side one.

This could be problematic if there are multiple people (asynchronously) editing the transcript and the server version has moved passed the local version. As the local version will be left behind.

To Reproduce
see above description

Expected behavior

To have a better for the component to handle saving that doesn't introduce bugs.

Screenshots

NA

Additional context

bbc/digital-paper-edit-electron#4
#177

[pietrop]

Options

Some options considered

1. move saving logic outside of the component

In current master to save to server the logic is already outside of the component using ref.

The suggestion is to revisit that, and move the logic for local storage saving outside of the component as an optional module available at user discretion.

This also leaves to the user(developer) the responsibility for the logic on what to do when local storage maxes out. As well as whether they'd rather use some other form of local storage, eg indexDb.

2. local vs server sync

• Find a way to handle changes from server and decide which one is latest to use.
• raising error if local storage is maxed out

3. leave as it is

👎

• loses support for multi user async collab on transcripts

---

other?