GitHub Community
Issue with JSON validation in Markdown code blocks #23409
-
|
Hi, I’m not sure if this is the best place to report it. But I think that I found an issue with JSON validation in Markdown files. The specific JSON code block seems to cause an issue with the validator, and in consequence, the rest of the Markdown file is marked an invalid, which seems like an unexpected behavior. The issue is visible in blame view and when referring to the source code in issues and pull requests. The very example of this behavior that I found: Direct link to the blame of the problematic file:  pegn/specPEGN is a universal notation for expressing any grammar without any specific implementation in mind. - pegn/spec Best regards, |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
|
The JSON isn’t terminated properly, and You can try reporting the problem to the GitHub feedback form: Share feedback - GitHub Support |
Beta Was this translation helpful? Give feedback.
-
|
I tested on a toy example, and it seems that you’re right. Closing opened blocks makes this bug disappear: Thanks for the link, I’ll report it 😃 |
Beta Was this translation helpful? Give feedback.
-
|
I noticed that just skipping the closing tags makes this issue to appear:
|
Beta Was this translation helpful? Give feedback.
The JSON isn’t terminated properly, and
...isn’t valid JSON syntax. I wonder if syntax highlighting would work correctly if you close the open JSON blocks after the ellipsis? But I agree that highlighting the rest of the file beyond the code block like invalid JSON is a bug. 😅You can try reporting the problem to the GitHub feedback form: Share feedback - GitHub Support