Add Settings option to allow custom heading ids (GitHub, kramdom, Docusaurus, etc)

[thadguidry]

Initial checklist

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

Problem

Environment

Windows 11
VSCode Insiders 1.109.0
Docusaurus 3.9.1
MDX for Visual Studio Code:

• Identifier: unifiedjs.vscode-mdx
• Version: 1.8.17

Summary

When working with Docusaurus documents in MDX and using the MDX extension for VSCode, I see Acorn parsing the { } curly braces as expressions and giving warnings in VSCode.

snippet from overview.mdx file using Docusaurus v3.9.1

I did notice a fixture note about a directive that hints at Acorn parsing anything between curly braces as an expression. https://github.com/mdx-js/mdx-analyzer/blob/main/fixtures/directive/directive.mdx

I would be nice to have a MDX Analyzer setting for VSCode extension that would be something like this:

mdx.validate.ignoreCustomHeaderIds : | ignore | hint | warning | error |

This setting would allow disabling Acorn parsing of anything between { } curly braces.

Current solutions

There might be some hidden setting for the micromark plugin that I am not aware of how to control?

Proposed solutions

I am unaware of any setting or adjustment I could make to the MDX for Visual Studio Code extension.

[remcohaszing]

Duplicate of #496

[github-actions]

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

[github-actions]

Hi! Thanks for taking the time to contribute!

Because we treat issues as our backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn’t an exact duplicate but is closely related.

Thanks,
— bb

[thadguidry]

Thanks @remcohaszing , I'll reach out to Docusaurus team to get you some help on #496 so we can give you a break on maintenance. :-) Do you mind if they chime in directly on #496 to provide some guidance? Would that be ok with you?