Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Discussion: Any plans to have the React Native Log plugin implement the Chrome Console API?
See original GitHub issueWhen I use Chrome as the debugger for my React Native app, I have access to the Chrome Console API. I tried out Flipper today and found that the React Native Log plugin is missing all of the features of Chrome’s console that make logging good.
Are there any plans to make the logger behave more like Chrome’s console? My main problem is the fact that when I do console.log(someObject), Flipper outputs someObject as unformatted JSON. If it is really long, it goes off the screen and there’s no way to see the information without copying it and pasting it into a text editor. Chrome, on the other hand, gives us an explorable object that is very nice.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:52
- Comments:15 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
This is currently holding me back from using logging from Flipper, I still open debugger to be able to see the explorable objects.
I’ll be making some improvements to the logs plugin soon and will look into the multiline issue as well