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.
Immediate window for quick debugging
See original GitHub issueIs this a bug report or a feature request?
Feature request 🎁
How the feature should work?
We console log most of the time to quickly see the values variables are holding. But it could be overwhelming to find the conole.log results when you have thousands of lines printed to the console.
This is a crazy idea to make that work with the luxury of the UI we have in majestic. You would still use the good old console.log but instead of logging just the value, you would prepend it with a unique pattern like #^<yourValue>^# or $#<yourValue>#$, then majestic would go pick these values up and show it you in a UI, as I call it, The debug window.
This is still an early idea. Will try to put together a POC and see how it goes.
Issue Analytics
- State:
- Created 6 years ago
- Comments:17 (17 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
Why not just use vscode-jest for that?
And this implementation does not require to use any special characters while logging as earlier planned. Using regex to figure out the logs from the output stream which is not very reliable, so experimental.
Jest team suggested to use setupFiles and override the console method to get hold of the console logs which would be more reliable so that’s an enhancement to address.