Commit f150749
committed
fix(docs-gen): escape {{ in generated API markdown prose
docfx preserves verbatim spec-marker text from XML doc comments like
"{{term(data set)}} of the number of {{termplural(Asset)}} ..."
in the generated `*.md` files. VitePress's underlying Vue template
compiler then treats `{{ ... }}` as a mustache interpolation and
tries to parse the contents as a JavaScript expression. Spec markers
contain unquoted spaces and operator-like tokens, so the parse fails
and the Docs-site CI's Build VitePress site job aborts with errors
like `Error parsing JavaScript expression: Unexpected token`.
Extend the post-processing awk pass to rewrite every `{{` outside
fenced code blocks as `{{`. The html-entity form survives
the markdown -> HTML pipeline and presents the original characters
to readers without engaging Vue's mustache parser. Standalone `}}`
is harmless once its opening `{{` is gone, so it is left alone.1 parent dcc4cdb commit f150749
1 file changed
Lines changed: 11 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
182 | 182 | | |
183 | 183 | | |
184 | 184 | | |
185 | | - | |
| 185 | + | |
| 186 | + | |
186 | 187 | | |
187 | 188 | | |
188 | 189 | | |
189 | 190 | | |
190 | 191 | | |
191 | | - | |
| 192 | + | |
| 193 | + | |
| 194 | + | |
| 195 | + | |
| 196 | + | |
| 197 | + | |
| 198 | + | |
| 199 | + | |
| 200 | + | |
192 | 201 | | |
193 | 202 | | |
194 | 203 | | |
| |||
0 commit comments