App is broken with old history in localStorage

[nickpalenchar]

Describe the bug
Starting after 271bd06 (or perhaps around then), old localStorage from a user agent causes the app to break when navigating to the app.

To Reproduce
Steps to reproduce the behavior:

1. Open the browser and open devTools
2. Go to the tab for storage, click on localstorage
3. Edit the history section to be [{"time":"2:57:54 PM","method":"POST","url":"https://reqres.in","path":"/api/users"},{"time":"2:56:30 PM","method":"GET","url":"https://reqres.in","path":"/api/users"},{"time":"10:33:28 AM","method":"GET","url":"https://reqres.in","path":"/api/users"}]
4. Go to the postwoman page to get the app to break

Expected behavior
The app should fully load, any old history that can't be deciphered should be displayed with as much information as possible.

Desktop (please complete the following information):

• OS: Mac OS Sierra
• Browser: Firefox
• Version 68.0 (64-bit)

[nickpalenchar]

FYI I have a working solution that I am preparing 😎

[liyasthomas]

I suspect this is the reason for few other issues that have reported and solved on flushing cache and local storage 🤔

Btw, these kinda people (@nickpalenchar) are 💎

[nickpalenchar]

Agreed it's most likely the cause of other people's issues re: clearing cache/storage. What's nice is this bug points out a clear area to tackle when thinking about tests re #65.

It would be awesome to have some sort of regression tests, but quick(er) win would probably be to start in an e2e testing--something that would verify there are only expected properties (adding new ones would be fine, but the contributor would then have to acknowledge the change by updating the tests.). But that's a discussion for another feature

[liyasthomas]

@all-contributors please add @nickpalenchar for code

[allcontributors]

@liyasthomas

We had trouble processing your request. Please try again later.