https://github.com/rust-analyzer/rust-analyzer/issues/1997 whats the best way of debugging the output of comments whilst working on the PR? i could run dbg!() but not sure where that would output too. Are people just rebuilding and re-installing the extension in vscode?
RA_LOG_DIR=1 worked for me
The best way would be to write a test
I think the best way to exercise this functionality is via hover test,like this one: https://github.com/rust-analyzer/rust-analyzer/blob/1f4fbc0035a6a9ee1b599a3aa9f236989633a9f7/crates/ra_ide_api/src/hover.rs#L474-L512
is not stripping tailing whitespace enough? Do we not need to replace trailing whitespace with a \n so vscode actually places the next line on a new line?
Hm, yeah, I think what we want for
/// hello /// world
I think there are some basic doc comment tests in
ast.rs that do not go through hover etc.
@Jason Williams These are the ones I am referring to: https://github.com/rust-analyzer/rust-analyzer/blob/master/crates/ra_syntax/src/ast.rs#L86-L195