A stringifier option to control escaping

[djmcgreal-cc]

Initial checklist

• I read the support docs
• I read the contributing guide
• I agree to follow the code of conduct
• I searched issues and couldn’t find anything (or linked relevant results below)

Problem

The stringifier is escaping in a way I find overzealous.

Is it for portability? I don't need portability for my case and find _SOME\_ITALICS\_WITH\_SPACES_ less readable and natural.

Solution

An option to control when things are escaped. I'd be happy with turning it off entirely but others might want more control for escaping in different scenarios.

Alternatives

Not sure?

[wooorm]

Hi!

What you want (breaking all markdown) is not possible.

There is already control in options: the Unsafe patterns.

If you want to improve how things are escaped and want to put in the work to do so, feel free to open a discussion and share your throughs on how to achieve that: https://github.com/syntax-tree/.github/blob/main/support.md

A similar discussion: syntax-tree/mdast-util-to-markdown#31

[Murderlon]

The easiest way to get rid of them if you must is to run Prettier after remark on the files. They have custom remark logic to undo the escapes.

[djmcgreal-cc]

Is it possible to use Join, Unsafe etc with a .remarkrc.yaml? Or is this only configurable from JS?

[wooorm]

JS, and it’s all complex. See the thread I linked.

[djmcgreal-cc]

Thanks for the help :)
PS I hope my small use case doesn't break all markdown, that would definitely be an unintended side-effect!

[wooorm]

PS I hope my small use case doesn't break all markdown, that would definitely be an unintended side-effect!

It’s like asking a JavaScript formatter to emit the string " unescaped. You’d get const x = """ for example. That breaks JavaScript. Same with markdown.

[HananoshikaYomaru]

The easiest way to get rid of them if you must is to run Prettier after remark on the files. They have custom remark logic to undo the escapes.

I don't see how, can you explain?