Page refresh should allow existing timers to continue running

[iteles]

For both anonymous and logged in people.

I think this needs to be an MVP feature because the people we will be lucky enough to have as our alpha users will be opening and closing tabs all the time!

[nelsonic]

Agree. will get this done today. 👍

[nelsonic]

@iteles should the timers be stored on the client (Offline: #35) or should just the session token be stored on the client and we send a GET /timer/all query during boot?
(one is a lot faster_er_ but means we don't fetch any timers that were created on a diff device/browser) ...

_Or... do we load from localStorage and _also GET /timer/all and re-render if there are more timers on the server than on the device...?

[nelsonic]

Need to get Login #106 working
then add a GET /timers/all request in loadtimers to ensure we fetch timers from the server if the person is logged in.

[nelsonic]

@iteles please test and close if happy.

[iteles]

Works perfectly, both the timer keeps running AND any description already entered into the active timer re-appears. 👍 😊

[nelsonic]

But... any previous timers (from an earlier session) were not being show (once the person logged in)...

[nelsonic]

@iteles Works now. steps to test this are:

• create timer as anon
• register
• create more timers
• refresh
• logout
• refresh
• create new timer
• refresh
• login
• refresh
  😉

[iteles]

I was still thinking along the lines of anonymous timers 😊
Caught another bug whilst testing this one: #122

Shall we call this one closed and leave the other issue to capture the remaining work @nelsonic?

[nelsonic]

_Nothing_ "Works" until _Everything_ (just) Works!
Investigating #122 now. 👍

[nelsonic]

@iteles do you have time to re-test this now?

[iteles]

Seems to be working well 👍