Incorrect handling of newlines in `/** */`-style docstrings

[epatters]

When tsify generates a doctring for a type definition, any newlines in the Rust doc comments appear as "\n" (two characters, "\" and "n") in the TypeScript docstring.

[siefkenj]

Hmmm. I know this was an issue with an old version of rust-analyzer. Can you verify that the produced .d.ts files have the \ and n in them?

[epatters]

I can confirm that, for this type, I'm seeing the characters \ and n in sequence in the generated .d.ts file. The long, multi-line doc-comment ends up as a one-line doc-string with the newlines appearing as \n.

Sorry, I know that's not a very self-contained example. I can try to produce a minimal example if it's helpful.

[siefkenj]

Can you test whether it still happens if you use triple slash /// for the doc comments?

[epatters]

That fixed it!

[siefkenj]

Great! I will leave this issue open because it really should work with /** */ style comments as well, but at least there is a workaround.

Let me know if you're interested in looking into a PR for this.