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
{{ message }}
This repository has been archived by the owner on Aug 13, 2018. It is now read-only.
It could be useful if the inline payload preview shows only actual user data. So, in case of Socket IO it would show only the 'data' field. I believe (according to a feedback I've got) that dev folks are mostly interested in the real data they are sending over the wire (not in the garbage appended by Socket IO)
This would require specific support for every protocol. But perhaps we can start with Socket IO and see how it works...
Thoughts?
Honza
The text was updated successfully, but these errors were encountered:
I haven't really worked much with Socket.IO, but if that is the case, then I totally agree. We should only show the info people are interested in in the inline previews. Especially since it should be really easy to peruse the list for the frame you are interested in. But I think we should still show the entire message in the sidebar, as some people may be interested in that.
It could be useful if the inline payload preview shows only actual user data. So, in case of Socket IO it would show only the 'data' field. I believe (according to a feedback I've got) that dev folks are mostly interested in the real data they are sending over the wire (not in the garbage appended by Socket IO)
This would require specific support for every protocol. But perhaps we can start with Socket IO and see how it works...
Thoughts?
Honza
The text was updated successfully, but these errors were encountered: