VSCode issue diagnosis
Closed this issue · 1 comments
gerard-ryan-immersaview commented
What is the problem you're trying to solve
There is no way in VSCode to diagnose issues.
As part of discovering #51, I ended up having to run cargo +nightly-2024-10-31 owl and reading the JSON to find out that there was no lifetime information available to display in test code.
Describe the solution you'd like
Some form of logging, #17 would be overkill for this issue.
Ideally in the output console for this extension like rust analyser.
But whatever is easiest to implement would suffice.
Additional context
No response
cordx56 commented
Implemented. It will be able to use in next release.
ref: #17 (comment)