[GH-ISSUE #534] Link validation triggers when PANDOC links refer to Zotero citations #2284

New issue

Closed

opened 2026-03-07 20:06:20 +03:00 by kerem · 4 comments

kerem commented

2026-03-07 20:06:20 +03:00

Owner

Originally created by @elonden on GitHub (Jun 28, 2022).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/534

When I insert a link definition like [@abc123] pandoc will look in my Zotero citation reference (bibtex) and insert a reference number pointing to a link at the end of my document.

Markdownlint does flag this as an error and mentions "no link definition found". As there is no MD number associated I can't exclude it. At least I haven't found a way to do this..

Any ideas would be much appreciated.

Regards
Erwin

Originally created by @elonden on GitHub (Jun 28, 2022). Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/534 When I insert a link definition like [@abc123] pandoc will look in my Zotero citation reference (bibtex) and insert a reference number pointing to a link at the end of my document. Markdownlint does flag this as an error and mentions "no link definition found". As there is no MD number associated I can't exclude it. At least I haven't found a way to do this.. Any ideas would be much appreciated. Regards Erwin

kerem

2026-03-07 20:06:20 +03:00

closed this issue
added the
question
label

kerem commented

2026-03-07 20:06:21 +03:00

Author

Owner

@DavidAnson commented on GitHub (Jun 28, 2022):

I'm not familiar with Zotero or bibtex, neither is part of the CommonMark specification as far as I know. You probably want to disable the relevant rule for your project, it sounds like MD052/reference-links-images, but the name can be found in the error you are getting.

@DavidAnson commented on GitHub (Jun 28, 2022): I'm not familiar with Zotero or bibtex, neither is part of the CommonMark specification as far as I know. You probably want to disable the relevant rule for your project, it sounds like MD052/reference-links-images, but the name can be found in the error you are getting.

kerem commented

2026-03-07 20:06:21 +03:00

Author

Owner

@elonden commented on GitHub (Jun 28, 2022):

Hello David,

This is the trigger I get:

It doesn't show an MD number so I'm a bit in limbo here.

@elonden commented on GitHub (Jun 28, 2022): Hello David, This is the trigger I get: ![image](https://user-images.githubusercontent.com/15621535/176100919-9fb39a34-5f45-4e38-81f3-c3af9f657839.png) It doesn't show an MD number so I'm a bit in limbo here.

kerem commented

2026-03-07 20:06:21 +03:00

Author

Owner

@DavidAnson commented on GitHub (Jun 28, 2022):

I don't think that error is coming from a built-in markdownlint rule:

The new rule is not yet available in the VS Code extension
The message from MD052 is worded differently: github.com/DavidAnson/markdownlint@51cec76c2b/lib/md052.js (L27)

I think you may be seeing new VS Code behavior: https://code.visualstudio.com/updates/v1_68#_markdown-link-validation

@DavidAnson commented on GitHub (Jun 28, 2022): I don't think that error is coming from a built-in markdownlint rule: 1. The new rule is not yet available in the VS Code extension 2. The message from MD052 is worded differently: https://github.com/DavidAnson/markdownlint/blob/51cec76c2b0e585a290aec4b53201c517e53d901/lib/md052.js#L27 I think you may be seeing new VS Code behavior: https://code.visualstudio.com/updates/v1_68#_markdown-link-validation

kerem commented

2026-03-07 20:06:21 +03:00

Author

Owner

@elonden commented on GitHub (Jun 28, 2022):

David, you are correct. A while ago I enabled the internal vscode experimental markdown validation. This is where that warning message came from. As I referenced these links somewhat differently before I did not notice this.

Now I've set this to ignore and things look a lot better.. :-)

Sorry for bothering. Maybe it'll help someone though...

Regards
Erwin

@elonden commented on GitHub (Jun 28, 2022): David, you are correct. A while ago I enabled the internal vscode experimental markdown validation. This is where that warning message came from. As I referenced these links somewhat differently before I did not notice this. ![image](https://user-images.githubusercontent.com/15621535/176108304-b47e56e3-c456-47df-baee-34c0fc4322ae.png) Now I've set this to ignore and things look a lot better.. :-) Sorry for bothering. Maybe it'll help someone though... Regards Erwin