JSON parse/stringify cache data in queries to avoid serialization error #1481
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #1479
#1418 did an optimization where only the data for the tab you're viewing is transferred between the content scripts and devtools. That data used to all be sent together and serialization errors were avoided by running a
JSON.parse(JSON.stringify(...))
on the entire data set. In making the change in #1418 however, it now only applies this to the cache tab data. We also send cache data for the queries tab which needs this fix as well.