fix: Fix panic on headers with no text content #56
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.
Fixes a panic when processing headers that contain only attributes (e.g., # {#custom-id}) or other non-text content.
Problem:
Headers with no Text or Code events would leave the span end at 0 while the start was a positive offset, causing a slice panic: begin <= end (16 <= 0) when slicing.
This can happen when an include file contains and the document has headers with only custom ID attributes.
Solution:
Includes a regression test.