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.
Add Refresh Support
See original GitHub issueVS Code now has an API to trigger a refresh, see https://github.com/microsoft/vscode/issues/139737. This would allow you to get rid of the “Reload Tests” command, hooking it up to the refresh button instead.
My main motivation for this is that if you use this also for rediscovering tests after e.g. the testMate.cpp.test.executables setting has changed, then apparently we would get a progress bar in this case too (see https://github.com/microsoft/vscode/issues/141182). I would find this very useful, as we have a ton of test runners and discovery can take a long time. And I’m changing testMate.cpp.test.executables very often.
Issue Analytics
- State:
- Created a year ago
- Comments:12 (12 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
Yes 😃
Especially because multiple workspaces can be opened at the same time and the extension tries to be smart and refresh only the one which has changed. The refreshHandler is a global request. I guess I could store some info to global variable but that could be called hacky.
The new progress bar and status reporting in 4.2.2 is very nice. Thanks!