You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It wasn't directly for race conditions only. It's like being able to export performance (flame) graphs in browser devtools.
It could be useful when discussing an issue to be able to view the same thing as what the reporting user is seeing. Trying to do this with screenshots and descriptions is difficult. The output from devtools makes a good timeline for what happens in Urql and the Urql cache when something goes wrong. Being able to export that allows a more knowledgeable user (e.g. an Urql maintainer or other dev) to import what happened and zoom in on the details that are important (without having to go back 'n forth to the reporting user).
Have an option in devtools to export the complete history (which is in state)
Have an option in devtools to import aforementioned export and see the history in the events view
In terms of whether we would do this or not, I'm totally sure of the value and I'd guess it would be a fair amount of effort. I'll leave it open anyhow to get thoughts from others!
In the meantime, I'd say there are a fair number of alternatives:
writing a small exchange to write events to a file (happy to help on this)
exporting network events as HAR using the chrome network tab
providing reproduction instructions to engineers
The conversation is still open so if you have a very clear idea of how this could be done and where this provides value, fight your case 👊
About
I'm currently trying to debug what appears to be a race condition and I'm unclear where the cause is.
It would be helpful if I could export the events that were registered by the devtools so that I could add this to a bug report/support request.
That would allow another developer to see the order of events and see what's happening and what's triggering the incorrect state.
The text was updated successfully, but these errors were encountered: