Ampersand in link query strings unexpectedly escaped with backslash about remark HOT 5 CLOSED

Mostly human error! 😅

We have a pipeline that pulls in some Markdown, processes with remark and a bunch of plugins, and then stores the resulting Markdown for rendering later. We were struggling with migrating some links where the search parameter syntax had changed and noticed “Oh there’s this \ in some of them after processing.” This led us to misattribute that as the cause for some link breaking (because naively copying a link like that does break) and debug to work out what was introducing the \ (assuming it to be one of our plugins, but later realising it was remark itself). You mentioned “Markdown parsers support escapes”, so that made me double check and realise this was the wrong rabbit hole and the final <a> in our rendered content was correct 😁

Anyway — appreciate your fast response. Helped get us back on track 💜

from remark.

Hey!

This is intentional. &, depending on what comes after it, could turn into a character reference. E.g., when copy; comes after it, it turns into something else.

breaking the link

The link is not broken. Markdown parsers support escapes.

For more info, see for example syntax-tree/mdast-util-to-markdown#53.

from remark.

Hi! This was closed. Team: If this was fixed, please add phase/solved. Otherwise, please add one of the no/* labels.

from remark.

Thanks for the response! My rehype pipeline is still ending up with the bad link in the rendered content, but I’ll dig a bit deeper to figure out that bit. Nope, this also wasn’t true, things are actually working as expected, we just misattributed the real cause of an error to that sneaky looking \. Apologies for the disturbance and thanks again! 🙌

from remark.

No worries!

Could you share the actual problem with me? I'd appreciate hearing your root cause for future strugglers!

from remark.