microsoft / microsoft/vscode-markdown-languageservice

`markdown.validate.referenceLinks.enabled` Improperly marking Jekyll YAML Headers as "No like definition found"

Open
#91 1 comment 0 reactions 1 assignee View on GitHub

@mjbvz is already working on this.

Since Nov 3, 2022.

bug
Dominant language
TypeScript
Stars
438
Forks
25
Avg merge
3d 21h
Merged PRs (30d)
1

Description

Type: Bug

  1. Have a jekyll YAML header in a markdown file like this
---
title:      Post Title Here
author:     Person Doe
categories: [catagory1, catagory2]
tags:       [tag1, tag2]
---
  1. The catagory and tags info within the [] will be marked as "No like definition found"

VS Code version: Code 1.73.0 (8fa188b2b301d36553cbc9ce1b0a146ccb93351f, 2022-11-01T15:38:50.881Z)
OS version: Darwin x64 21.6.0
Modes:
Sandboxed: No

System Info
Item Value
CPUs Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz (12 x 2900)
GPU Status 2d_canvas: enabled
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_renderer: enabled_on
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off
Load (avg) 3, 2, 2
Memory (System) 32.00GB (10.15GB free)
Process Argv .
Screen Reader no
VM 0%
Extensions (52)
Extension Author (truncated) Version
better-comments aar 3.0.2
Bookmarks ale 13.3.1
preview-mp4 ana 0.0.1
converttoasciiart Bit 1.0.3
doxdocgen csc 1.4.0
vscode-markdownlint Dav 0.48.1
gitlens eam 13.0.3
prettier-vscode esb 9.9.0
linter-gfortran for 3.2.0
pythonsnippets frh 1.0.2
ginfuru-vscode-jekyll-syntax gin 0.1.1
todo-tree Gru 0.0.219
fortran-ls han 0.6.2
jenkinsfile-support ivo 1.1.0
vscode-edit-csv jan 0.7.2
better-cpp-syntax jef 1.16.3
vsc-python-indent Kev 1.18.0
vscode-cudacpp kri 0.1.1
vscode-hdf5-viewer loc 0.0.3
bash-ide-vscode mad 1.14.0
vscode-autohotkey-plus-plus mar 3.0.0
git-graph mhu 1.30.0
anaconda-extension-pack ms- 1.0.1
isort ms- 2022.4.0
python ms- 2022.18.0
vscode-pylance ms- 2022.11.10
jupyter ms- 2022.9.1202862440
jupyter-keymap ms- 1.0.0
jupyter-renderers ms- 1.0.12
vscode-jupyter-cell-tags ms- 0.1.6
vscode-jupyter-slideshow ms- 0.1.5
remote-containers ms- 0.262.3
remote-ssh ms- 0.90.1
remote-ssh-edit ms- 0.84.0
remote-wsl ms- 0.72.0
vscode-remote-extensionpack ms- 0.21.0
cpptools ms- 1.12.4
vsliveshare ms- 1.0.5750
autodocstring njp 0.6.1
clang-tidy not 0.5.1
nsight-vscode-edition nvi 2022.2.31663688
material-icon-theme PKi 4.21.0
trailing-spaces sha 0.4.1
rewrap stk 1.16.3
code-spell-checker str 2.10.1
cmantic tde 0.9.0
pdf tom 1.2.0
latex-support tor 3.10.0
errorlens use 3.6.0
snippet-creator vin 1.1.0
better-align wwm 1.1.6
markdown-all-in-one yzh 3.4.3

(5 theme extensions excluded)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.