Closed noppej closed 1 year ago
I added a few nits that are not a must but would be nice :)
I added a few nits that are not a must but would be nice :)
Much appreciated ... nits or not, they help improve code quality, and worth the few minutes it takes to address. Thanks !
Build succeeded:
probe-rs
recently adopted thetracing
crate for logging. This opened up the possibility to cleanup how logging was implemented in the VSCode extension and associatedprobe-rs-debugger
.This PR will do the following:
launch.json
setting to directprobe-rs
logging to a JSON file, which can later be analyzed with the log viewer.probe-rs
(RUST_LOG) logging from the data being reported in the VSCode debug console. It is currently interspersed with debug adapter logging, and although somewhat informative, it makes it less than useful when analyzingprobe-rs
specific issues.probe-rs-debugger
handling of MS DAP events and messages, to be more useful (objective opinion) to users of the extension.probe-rs-debugger
logging will happen according to these rules:LevelFilter
to configure a subscriber that logs to a file in the system's application data directory.LevelFilter::ERROR
to stderr (because these errors are picked up and reported to the user by the VSCode extension).NOTE This release requires changes to the
launch.json
files in user projectsconsoleLog
property only supports one of three values[Console, Info, Debug]
env
properties, for example:For testing, feel free to use the extension binary