Add a wrapper around Chrome Storage API

[maxpatiiuk]

Integrate with Google Drive API so that extension can store it's data there

[maxpatiiuk]

Actually, integrating with Google Drive is not needed because extensions already have access to storage API - https://developer.chrome.com/docs/extensions/reference/storage/

Extensions can sync storage data between all devices, or keep data local.

There is a quota limit on the storage, but if we run out, there is a unlimitedStorage permission we can request

[maxpatiiuk]

@Durbatuluk1701 Integrating with Google Drive API won't be needed.

But, we will need a cache layer to save the computed summary of how much time the user spent on a particular event in a given week

[Durbatuluk1701]

@maxpatiiuk Nice hopefully that should be simpler if I am understanding correctly?

[maxpatiiuk]

Yes!

Here is probably the best solution to this:

You could implement this using incremental synchronization - https://developers.google.com/calendar/api/guides/sync

I.e, our extension computes the stats for each day for every calendar for the last 4 years, and stores that locally.

Then, once an hour or once a day it recomputes the stats for the changed days using the calendar synchronization endpoint

Another solution:

Fetch data one day at a time. Save computed events locally. Assume that past events do not change, and thus can be cached forever. Don't cache future events as they are likely to change.

Also, need to figure out some cache busting strategy (or at least a "clear cache" button in the UI)

[Durbatuluk1701]

Okay sounds good. I will look into implementing that this week. Sorry I didn't make much progress last week, I was extremely busy.

…

On Oct 2, 2022, at 9:10 AM, Max Patiiuk ***@***.***> wrote:  Yes! Here is probably the best solution to this: You could implement this using incremental synchronization - https://developers.google.com/calendar/api/guides/sync I.e, our extension computes the stats for each day for every calendar for the last 4 years, and stores that locally. Then, once an hour or once a day it recomputes the stats for the changed days using the calendar synchronization endpoint Another solution: Fetch data one day at a time. Save computed events locally. Assume that past events do not change, and thus can be cached forever. Don't cache future events as they are likely to change. Also, need to figure out some cache busting strategy (or at least a "clear cache" button in the UI) — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.

[Durbatuluk1701]

CLosed by #80