Tables over about 3,000 rows are written as divs because Markdig cannot read them back

Open
  • Is something wrong?
#43 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp
Domain
backend

Research direction

Start by reading the table writer's read-back check and how it falls back to divs; the issue does not name the relevant files or tests. Reproduce the failure with a pipe table of roughly 3,000 rows, then inspect Markdig's size or depth guard. Decide whether to split long tables, report a Markdig finding, or document the limit, and verify that the chosen behavior handles the large table.

Written by the indexing model from the issue text.

Description

textediting

Found while fixing sillsdev/SIL.TextEditing#141 (PR sillsdev/SIL.TextEditing#143): above roughly 3,000 rows Markdig fails to read a pipe table back, so the writer's read-back check rejects it and falls back to divs. Find Markdig's limit (depth/size guard?), decide whether to split long tables, raise a finding, or document the limit. Relevant to the tables work (report 19).

Dominant language
C#
Stars
1
Forks
0
Avg merge
3h 55m
Merged PRs (30d)
36

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sillsdev/motif

All issues in sillsdev/motif

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.