As we’re getting close to rounding out the Beta period of the 2.0 editor, we’re trying to close out any bugs we find or users report quickly. They could be browser-support related, network conditions related, account capability related, or just bugs in how the 2.0 editor and technology behind it works. It’s complicated enough that the best way to debug things is to see exactly what the user sees when they have trouble.
A very cool side effect to having built the 2.0 editor with Apollo is that we have a nearly complete look at what is happening in the editor by virtue of the Apollo Cache (we talked about what that is here). We built a tool that can export that as JSON data, and we can load it locally to see exactly what the user sees. It’s a bit fancier than that, doing things like saving browser console error logs and stuff, but that’s the gist of it.
Time Jumps
- 00:00:06 Debug logs
- 00:02:53 How to join the CodePen Discord
- 00:03:56 A super version of it for ourselves
- 00:07:12 What we do with the data logs
- 00:08:55 The importance of supporting versions
- 00:11:45 We can see the debug in a live version of the editor
- 00:14:12 Client side and then adding server side