Open jmooring opened 3 months ago
Perhaps we can just have separate syntax validator tool, instead of whole server routine
syntax validator tool
There's nothing invalid about the unclosed fenced code blocks that you described in the original forum topic. It may not be what you intend, but the markdown itself is valid.
Perhaps you can find a linter that warns you about unclosed fenced code blocks, but the best known linter (markdownlint) does not have this capability. See:
https://github.com/DavidAnson/markdownlint/issues/331
This issue is not related to unclosed fenced code blocks in any way.
Ok, as I understand this syntax is correct:
```json
{{< sc >}}
```
The issue is that Hugo just throws panic
Maybe I can just write Java application which can find all such specific patterns and report... with IDE, I am more or less successful and fast using search for "json" in files; but initially I was doing "binary search" to find why it fails, removing half of files then starting server until I find suspect.
I didn't see such issue with other patterns such as "mermaid"; only with "json".
I didn't see such issue with other patterns such as "mermaid"; only with "json".
That's why the issue title is:
Error when JSON fenced code block contains shortcode call
It is specific to fenced code blocks where the language portion of the info string is "JSON".
Reference: https://discourse.gohugo.io/t/panic-with-json-and-workaround-but-better-to-fix-it/50137/9
markdown