Repository navigation
fix: keep content before the next heading when slicing tokens - #223
Merged
Merged
Conversation
findContentAfterList and findContentAfterHeadingClose computed the end index relative to a slice but used it as an absolute index, dropping the token before the next heading (often a code fence) or emptying the description entirely for structures and events. Assisted-by: Claude Fable 5.1
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
erickzhao
approved these changes
Oct 28, 2026
|
🎉 This PR is included in version 3.0.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
findContentAfterListandfindContentAfterHeadingClosecomputed the end index relative to a slice but used it as an absolute index, dropping the token before the next heading (often a code fence) or emptying the description entirely for structures and events.Claude did an analysis and says this is currently causing some of our docs content to be truncated when parsing the docs, mostly trailing code fences.