Local restore and backup.

[digi0ps]

Forked off #709.

@oliversauter Ticked off most of the things in the list you made in the previous PR.

Remaining:

if user makes their first backup, no matter if they restored before or not, it should give them the choice to setup the path again.

Don't exactlly get this. Do you mean change the choice of backend or change the local backup? Both are possible right now, if you click the "change" button.

• @ShishKabab it still does not store the 'images' folder in the local backup. Wasn't that supposed to be in with Structure of local backup is now identical to GDrive backup #698? If so @digi0ps could you check if you maybe not accidentally reverted some changes?

I don't think I deleted any restore code as such. But a rebase error might have happened. @ShishKabab can you check when you are free?

[blackforestboi]

From a UX and UI perspective this is ready to go into production.

However there are still some oddities: I did a full restore with my 2gb data library from G Drive too and all worked well without errors. 👍 However there is

1. some data missing. It does not show me pages from the last 5 days, and a lot of screenshots are missing too.
2. more data in my restored version than in my original one headscratch

I feel like before we start implementing the syncing problem (or as part of it), we should make sure that we figure out those indexedDB oddities somehow, and if those are not the cause then make really sure that all data is properly backed up and restored.

Will now do a backup to my local hard drive to compare and can more tomorrow.

[blackforestboi]

Ok some more data:

Good news:

• It seems as if all pages and other documents are properly backed up and restored

Bad news:

• It seems like that is not the case for screenshots. A lot of them get lost in the process.
• There are still some discrepancies between GDrive and local backup. I can't figure out why I have this hole of 600 pages missing, but just in the last week. There was no data loss when using the local app to backup & restore. Will do another Backup on Google Drive and see what the result is.

Setup:

1. Main Extension 24100 pages
2. Google Drive Account with (allegedly 3gb) of data
3. New extension used for restore & Backup: 23599 pages

• Backup Size calculation: 1800mb images, 400mb rest
• Actual Backup on disk: 700mb images, 400mb rest

[ShishKabab]

before we start implementing the syncing problem (or as part of it), we should make sure that we figure out those indexedDB oddities somehow.

Yup, that's one thing we've learned from this whole adventure. The new sync tech sits in front of Dexie, captures all modifications, and turns them into transactions that contain the original write and the write to the sync log. That we we're always 100% sure each and every change is logged.

(Right now we're using Dexie hooks, which are more unpredictable it seems. Plus, they're not portable to different databases.)

[blackforestboi]

Thanks @digi0ps for the awesome work to finish this one up :) ready to launch baby!