Skip to content

Optimise table row preparation for document fragment batches - #550

Merged
g105b merged 1 commit into
masterfrom
test/492-table-fragment-binding
Nov 11, 2026
Merged

g105b merged 1 commit into
masterfrom
test/492-table-fragment-binding

Conversation

@g105b

@g105b g105b commented Nov 10, 2026

Copy link
Copy Markdown
Member

Keeps table rows batched in a DocumentFragment, resolving the row template once per batch rather than once per row. Header-only tables skip row preparation.

Tests cover detached binding, row order, repeated batches, existing rows and filter failures without partial output. The template lookup regression test fails on master. All 355 tests and static checks pass; local statement coverage increases slightly from 99.655884% to 99.656357%.

Fixes #492.

@codacy-production

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric Results
Complexity 0
Duplication 0

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

@g105b
g105b merged commit 802e66d into master Nov 11, 2026
53 checks passed
@g105b
g105b deleted the test/492-table-fragment-binding branch November 11, 2026 10:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Optimisation: bindTable should use DocumentFragment

1 participant