Turning off parsing markup features like headers, image urls, html tags

[Nukiloco]

Hi I was wondering. How do you turn off certain markup features in unified? For example I want to turn off headers, image urls, and html tags (in the markdown input) from being parsed at all and instead get treated like its regular text. Thanks!

[ChristianMurphy]

Sounds like micromark/micromark#31 and/or remarkjs/remark#552

[Nukiloco]

remark-disable-tokenizers plugin doesn't work with the newer versions of remark which is sort of exactly what I want to use
is there any other way to disable block or inline tokens?

The extensions disable null method from micromark/micromark@21fecde also doesn't seem to affect or turn off any markdown thats being parsed at all

[Nukiloco]

Basically what I'm trying to achieve is multiple things.
First to disable these features:

• headers
• mail urls
• markdown image urls [aka ![img](url)]
• markdown urls (aka [test](url) which would turn into a url with the text of test)
• tables
• code blocks

And then im also trying to add these features:

• auto embed detection for urls
• examples of auto embed detection:
  • https://via.placeholder.com/180.png would replace the url with an image instead
  • someurl/video.png would replace the url with an video instead
• user mentions (kind of like github/discord/twitter)

[wooorm]

Why do you want to turn most of markdown off — what is the point in using markdown then?
What about your users? They’d expect certain things to work, but then they don’t?
Why do you want to turn all these things off?

[Nukiloco]

I'm using markdown as the base for a comment system though as a personal preference I'm also turning off some features as well that wouldn't fit with the type of website I'm trying to make. Basically I want people to have a little bit of customization on their comments, but not to a full extent, kind of like how Discord does their comment system which has some features enabled for markdown but not all them.

[wooorm]

I strongly recommend you don’t do this — instead of arbitrarily breaking much of a users expectations you can also support all of commonmark and perhaps a bit of GFM on top.
But it’s possible. You can turn constructs off with micromark (§ Case: turn off constructs) and you can wrap such extensions up in a remark plugin as well.

[Nukiloco]

Thing is, the website that I'm making won't say it supports markdown, it will just say that it supports custom formatting in comments. Basically I'm using a markdown parser to make my comment system.