xoofx / xoofx/markdig

GridTable Parser - wrong behavior while last cell is opened / not closed by a pipe

Open
#494 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C#
Stars
5.3k
Forks
510
Avg merge
8d 5h
Merged PRs (30d)
5

Description

GridTable Parser - wrong behavior while last cell is opened / not closed by a pipe

image

#### Overview of components
+-----+---------------------------------------+---------------------+----------+
| No. | component                             | comp. no.           |  count
+=====+=======================================+=====================+==========+
| 1   | component 1                           | xxxx-xxxx-xxxx      |  1
+-----+---------------------------------------+---------------------+----------+
| 6   | component 1                           | xxxx-xxxx-xxxx      |  1
|     | FW V01.00                             |                     | 
+-----+---------------------------------------+---------------------+----------+
| 7   | component 1                           | xxxx-xxxx-xxxx      | 1
| 2   | FW V01.00                             |                     | 
+-----+---------------------------------------+---------------------+----------+

Adding a with space behint the "1" will solve it - just curios :-)
It happens while parsing the table - tried to fix it, but without any success

Contributor guide

Open the 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.

Research direction

Start at the GridTable Parser entry point and reproduce the issue with the table shown in the report, comparing input with and without the trailing space after the final cell value. Trace how the unclosed last cell is parsed; done means the table is handled correctly without requiring that extra space, with regression coverage for the example.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.