chore: release 0.4.1#11
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Patch release: fix spanning body cells duplicated across columns on multi-page merge.
Fix
Docling represents a
col_span=Ncell by repeating its text across every column it covers. The merge round-trip (grid → DataFrame → grid) flattened those intoNseparatecol_span=1cells — duplicating a full-width description into every value column and displacing the real rate/cap values. A repeated multi-row header (col_span=6banner) flowing in as a body row behaved the same way._dataframe_to_docling_datanow matches each merged row back to its source grid row (across all member fragments) and re-emits the original spans. Rows the merger genuinely transformed (stitched continuations, folded overflow) fall back to the previous flat 1x1 rebuild. The match keys on original span metadata, never value equality, so coincidentally-equal adjacent values (two plan columns sharing a cap) stay separate cells.No changes to the extractor or the merger.
Tests
col_span=7descriptions andcol_span=6repeated headers now preserved; rate/cap land in the correct plan columns.🤖 Generated with Claude Code