Flipper: Question: Dev-Tools and browsing in bigger Object-Structures

[xstable]

In react-native-debugger it was quite easy to browse inside an Object which was written to console via "console.log".

How can I archive this in flipper? I didn't yet found any way to have the same result.
The "Log" section seems not to be the same.

[passy]

This has come up before. @mweststrate we still have this as a rough idea on the roadmap somewhere, don't we?

[mweststrate]

I don't have any immediate plans to implement, but to make it work we need a small protocol to be able to inspect objects lazily and transfer them piecemeal over the wire upon expansion. So that would require storing all object structures in a (time limited?) map under a random identifier, and establish a protocol where only the identifiers are send across the wire initially, and flipper can request for more data lazily.

If someone wants to implement that, help is definitely welcome, I'll happily review!

[stale[bot]]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions.

[mweststrate]

For completeness sake, note that the Hermes Debugger (in Flipper) is the same debugger as shown in the React Native Debugger, so for Hermes users you can access the logs similarly by using the Hermes Debugger plugin (provided that RND isn't running at the same time, as only one debugger can be attached).

For showing objects fully in in Logs / non Hermes engines, see #1010