Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Markdown lint for links is not correct. #96

Open
krave1986 opened this issue Nov 14, 2022 · 1 comment
Open

Markdown lint for links is not correct. #96

krave1986 opened this issue Nov 14, 2022 · 1 comment
Assignees
@mjbvz
Labels
bug Issue identified by VS Code Team member as probable bug
Milestone
Backlog

Comments

@krave1986
Copy link

Does this issue occur when all extensions are disabled?: Yes/No

This is the markdown link I wrote

### [fs.openSync(path[,flags[,mode]])](https://nodejs.org/api/fs.html#fsopensyncpath-flags-mode)

VS Code linter complains that link.no-such-reference
image

  • VS Code Version: 1.73.1
  • OS Version: Windows_NT x64 10.0.19044

Steps to Reproduce:

  1. Create a markdown file
  2. Copy this code into the file 
    ### [fs.openSync(path[,flags[,mode]])](https://nodejs.org/api/fs.html#fsopensyncpath-flags-mode)
@mjbvz mjbvz transferred this issue from microsoft/vscode Nov 14, 2022
@mjbvz mjbvz added the bug Issue identified by VS Code Team member as probable bug label Dec 5, 2022
@mjbvz
Copy link
Contributor

mjbvz commented Dec 5, 2022

Related to #7

@mjbvz mjbvz added this to the Backlog milestone Dec 6, 2023
@firxworx firxworx mentioned this issue Apr 14, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mjbvz mjbvz

Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
2 participants
@mjbvz @krave1986