fix: strip leading UTF-8 BOM from aggregated GitHub content#43
Merged
Conversation
The GitHub API returns file bytes verbatim, so a UTF-8 BOM in a source file (e.g. an extension's Docs/pages/00-index.md) survived decoding and landed at the start of the rendered page. A leading BOM before the first markdown heading stops Docusaurus from parsing it (the heading renders as a literal paragraph) and also breaks StripReadmeFront's H1 detection, since char.IsWhiteSpace(U+FEFF) is false. Drop it once at the single Base64Decode chokepoint so every aggregated file and README is BOM-free.
vbreuss
enabled auto-merge (squash)
June 4, 2026 18:31
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.
The GitHub API returns file bytes verbatim, so a UTF-8 BOM in a source file (e.g. an extension's Docs/pages/00-index.md) survived decoding and landed at the start of the rendered page. A leading BOM before the first markdown heading stops Docusaurus from parsing it (the heading renders as a literal paragraph) and also breaks StripReadmeFront's H1 detection, since char.IsWhiteSpace(U+FEFF) is false. Drop it once at the single Base64Decode chokepoint so every aggregated file and README is BOM-free.