[Feature Request] Provide method for converting callstack entry to location
See original GitHub issueThis will allow the clients to make the links in the output clickable: E. g.
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
I think that it might be possible to implement this on client-side by parsing the message and then using workspace/symbols but maybe it makes more sense to implement that on the server.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:8 (8 by maintainers)
Top Results From Across the Web
End October 2020 Milestone - GitHub
[Feature Request] Provide method for converting callstack entry to location enhancement. #1202 by yyoncho was closed on Nov 2, 2020.
Read more >How can I convert a stack trace to a string? - java
One can use the following method to convert an Exception stack trace to String . This class is available in Apache commons-lang which...
Read more >Understanding and Leveraging the Java Stack Trace - Stackify
Simply put, a stack trace is a representation of a call stack at a certain point in time, with each element representing a...
Read more >JavaScript debugging reference - Chrome Developers
Discover new debugging workflows in this comprehensive reference of Chrome DevTools debugging features.
Read more >Create a visual map of the call stack - Visual Studio (Windows)
Create a code map to visually trace the call stack while you're debugging. You can make notes on the map to track what...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I’m working on this.
In that case, I would be fine with just submitting the current “source container” logic and add the SearchEngine logic at a later point (if performance demands it).