Fix invalid YAML front matter for terms with no tags#408
Merged
Conversation
A term with an empty Tags list still had its ID-prefix tag appended onto
an empty CSV string, producing "tags: [,VFB]". The leading comma is an
empty flow-sequence node, which go-yaml rejects ("did not find expected
node content"), failing the Hugo build on VFB_00017893_v8.md.
Build the tag list properly and drop empty entries before joining.
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.
A term with an empty
Tagslist still had its ID-prefix tag appended onto an empty CSV string invfbterms.py, producingtags: [,VFB]. The leading comma is an empty flow-sequence node, which go-yaml rejects ("did not find expected node content"), failing the Hugo build onVFB_00017893_v8.md.Fix: build the tag list properly and drop empty entries before joining, so a leading/trailing comma can't be emitted for any input.
Note for deploy: existing
*_v8.mdalready present in the build workspace are not regenerated bysave_terms(it skips files that exist until the version bumps), so they must be swept separately: