docs: fix Jekyll Liquid build error in plan-execute.md#276
Open
v1r3n wants to merge 1 commit into
Open
Conversation
The pages-build-deployment workflow was failing with a Liquid syntax
error: the f-string code sample f'{{"path": "out/{i}.md", ...}}' in
the parallel-work example was parsed as an (unterminated) Liquid
variable. Wrap the code block in raw/endraw so Jekyll emits it verbatim.
This is the only Liquid-breaking token in the rendered docs set
(top-level + concepts/ + examples/); design/sdk-design docs have no
front matter and are copied without Liquid processing.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The
pages-build-deployment(GitHub Pages / Jekyll) workflow is failing onmain:The parallel-work code sample in
docs/concepts/plan-execute.mdcontains a Python f-stringf'{{"path": "out/{i}.md", ...}}'. Jekyll runs Liquid over fenced code blocks too, so the{{is parsed as an (unterminated) Liquid variable and the whole site build aborts.Fix
Wrap that code block in
{% raw %}/{% endraw %}so Jekyll emits it verbatim. Two-line change.Scope check
This is the only Liquid-breaking
{{/{%token in the rendered docs set (top-level*.md+concepts/+examples/— the dirs Jekyll actually renders, per the build log). The{{...}}tokens indocs/sdk-design/anddocs/design/plans/are harmless: those files have no YAML front matter, so Jekyll copies them without Liquid processing. The mermaid{{"text"}}diagrams render fine (valid Liquid string output).