-
-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrapping Markdown file with reference link messes up the links #93
Comments
Same thing when I used this extension to rewrap https://github.com/fastify/fastify/blob/1b49c5b698ad0727ce18efff852d8a703c67be94/docs/TypeScript.md?plain=1#L1232-L1258 I'd love to contribute a fix, but I have no idea what language this is https://github.com/stkb/Rewrap/blob/dec4de5daea0dd8caeed53ff1c1c39cd2bd4573f/core/Parsing.Markdown.fs |
Hi, I'd missed this issue; it's a duplicate of #63. This is fixed in the next version: you can download & install v1.16.0-beta.2 if you like. I tried rewrapping the file you linked and it all seemed to look fine. (Technically it doesn't yet follow the specs for link reference definitions exactly but it should be fine unless you "try to break it".) |
- New architecture (still WIP) with performance increase. - Markdown: new parser that fixes many small bugs (inc #288), as well as supporting: - Front matter header (#277, #294) - Link reference definitions (#63, #93) - Footnotes (#188) - ReStructuredText support (standalone & for Python, almost complete) (#88). - Julia: support `#= ... =#` block comments (#302) - Visual Studio: Wrap to rulers generated from .editorconfig by the Editor Guidelines extension (thereby indirectly supporting .editorconfig) (#300).
Fixed in v1.16.0 |
@stkb thanks for the release. Sorry I never tested the beta. I just didn't ever find the time. |
Hi @stkb, is it viable to make this work in markdown in comment? Currently it still messes link references in comments. |
Say I have a list of links like so:
When I wrap this, I get:
Resulting in broken links.
The text was updated successfully, but these errors were encountered: