Repository navigation
fix(export): footnote block edge cases and caption sanitizing - #23
Merged
Merged
Conversation
…nd loose footnote text, sanitize captions Follow-up to #22 from review: [n] went onto the first <p> even when a list came first; the duplicate-paragraph filter dropped a footnote whose text matched another's; text loose beside a footnote block was lost; caption markup was copied verbatim (now only a/em/i/strong/b/br survive).
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.
Follow-up to #22 from code review, each with a failing test first:
<p>[n]</p>instead of numbering a later paragraph.a, em, i, strong, b, br; script/img/iframe etc. are removed.Live post export (agentics-using-ai-should-be-joyful) is byte-identical to #22's.
npm test78/78, lint and tsc clean,distrebuilt.