Currently, even when the page transition happens when the user creates or deletes an entry, the autosave timer is not cleared.
Duplicated entry mechanism:
Open editor to create a new entry
Edit the content (starts autosave timer)
Click floppy button (starts save sequence and calls createRecord)
After saving, the page transition occurs
After 10 sec from 2, autosave timer fires. The timer function does not know the newly given rkey. Therefore it calls createRecord, resulting in duplicated entry
Undeletable entry mechanism:
Open editor to open an existing entry
Edit something (starts autosave timer)
Click delete
After deleting, the page transition occurs
After 10 sec from 2, autosave timer fires. This calls putRecord and deleted entry is recovered.
Furthermore, when there are duplicated entries and the user tries to resolve the rkey from entry name, the server-side remembers rkey of that entry because of cache mechanism of Next.js.
If the user deletes that entry, the server still uses old name-rkey correspondence.
Currently, even when the page transition happens when the user creates or deletes an entry, the autosave timer is not cleared. Duplicated entry mechanism:
createRecord)createRecord, resulting in duplicated entryUndeletable entry mechanism:
putRecordand deleted entry is recovered.Furthermore, when there are duplicated entries and the user tries to resolve the rkey from entry name, the server-side remembers
rkeyof that entry because of cache mechanism of Next.js. If the user deletes that entry, the server still uses old name-rkey correspondence.This PR addresses the problems above.