We recently found out that removing the JSON.stringify in #1245 caused some issues related to transporting the cache to the devtools. Unfortunately we could not catch this in development/testing because we don't have a sample application that provides some of the irregularities we see in real world apps. This is also very difficult to test in an automated way because there is virtually no way to run an automated end-to-end test for a browser extension.
Our next best option would be to create a development app that we can fill with some of these edge cases so that we can test these ourselves before we release.
We recently found out that removing the
JSON.stringifyin #1245 caused some issues related to transporting the cache to the devtools. Unfortunately we could not catch this in development/testing because we don't have a sample application that provides some of the irregularities we see in real world apps. This is also very difficult to test in an automated way because there is virtually no way to run an automated end-to-end test for a browser extension.Our next best option would be to create a development app that we can fill with some of these edge cases so that we can test these ourselves before we release.