Repository navigation
CLI reference: the global flags table rendered as a raw template - #89
Merged
Merged
Conversation
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
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.
The live CLI reference showed
{% for row in global_flags %}| {{ row.flag }} | {{ row.effect }} |instead of the global flags table. The site is built with zensical, which doesn't run themacrosplugin, and--strictdidn't notice.reference/cli.md: the four global flags are written out as a plain table. It was the only page using macros.docs/_data/cli-global-flags.yaml, themacrosplugin config and itsmkdocs-macros-plugindependency (poetry.lockre-locked).check-cli-drift.pynow reads only the page, andcli-drift.ymlno longer watches the YAML.docs.yml: after the build, any{{or{%left in a built page fails it. With the old page restored, the guard fires onreference/cli/index.html. With the fix, the site is clean.Checked locally: the strict build passes,
search.jsonis still produced, andcheck-cli-drift.pyreports no drift against comline 0.2.0.