Disabling auto-links with GFM

[ClementEXWiki]

Hi, I'm currently trying to use remark to parse some Markdown files and get an AST to then use them in various rich text editors.

One problem I have is that I'd like to have GFM support but also disable autolinks. Would that be possible?

I didn't find a way to do it in the options of remark-gfm.

Thanks in advance for your help! :)

[ChristianMurphy]

Can you expand on what you mean by disable auto links? And why you want them disabled?

GFM include autolinks so not having them is not having GFM.
As a whole we wouldn't recommend creating yet another markdown flavor https://github.com/micromark/micromark?tab=readme-ov-file#extending-markdown
It is possible https://github.com/micromark/micromark?tab=readme-ov-file#case-turn-off-constructs but something you may want to consider alternatives to.

[ClementEXWiki]

The syntax is not grammatical, but code; you in this example also used code. That’s what I recommend.
Sorry, I don't get what you mean?

Thousands of files can be changed! You could use remark to find these instances and edit those files.
I didn't explain myself properly ; I meant that some files are located in other people's backends, which we don't have access to, and cannot modify either since other tools are relying on this specific format.

If you add GFM, or some other standard, things will break anyway.
If you add GFM minus autolinks, congratulations: you invented a new standard. Things will break in other tools.
I only need to have compatibility with our own tools, not with other tools. This is indeed a derivative standard that's not 100% GFM, and I think it could have been done in a better way in the past, but unfortunately it is what it is today and I can't to anything about it as backwards compatibility must, as I said, be preserved.

[wooorm]

a) use semantic HTML/markdown: code, backticks.
b) that will keep on happening with your own standard
c) well you are discussing here to talk about compatibility with tools! you indeed do not need to solve things now, but someone will run into things in 4 years, and in 8 years, and ...

[ClementEXWiki]

I don't know how to explain it clearly (english is not my first language), but it basically goes like this:

• A custom format was created in the software I work on some 15 years ago (or so)
• This format is used by thousands of persons, with their own data which we can't replace now
• The format basically never changed since its creation (AFAIK), there is a special syntax to add new kind of instructions if required
• We need to maintain compatibility with documents written 15 years ago, which used that syntax

[wooorm]

I think I get it — I am trying to say that you cannot use standards such as GFM or CM if you have a custom format, and it is not my goal to support every company’s custom flavor, it is my goal to support standards.
You could use a version field to treat old and new content differently, and you could change the old documents to match new content.