You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current implementation of the Markdown tokenizer has limited support for parsing list items. At present, it only recognizes unordered lists that use - as the list marker. For example, the following is successfully tokenized:
- Item 1
- Item 2
However, the tokenizer does not support ordered lists, which are an essential feature of Markdown. This includes lists using numeric markers followed by a period, such as:
1. First item
2. Second item
3. Third item
Expected Behavior
The tokenizer should be able to recognize and generate tokens for both unordered and ordered lists, ensuring consistent handling of list structures. This includes:
Ordered lists with numeric markers (e.g., 1., 2.).
Lists with varying indentation levels to support nested lists (both ordered and unordered).
Impact
Currently, ordered lists are entirely ignored or misinterpreted during tokenization. This limits the functionality and correctness of the Markdown parser, leading to incomplete rendering in downstream applications such as PDF generation or HTML rendering.
The text was updated successfully, but these errors were encountered:
The current implementation of the Markdown tokenizer has limited support for parsing list items. At present, it only recognizes unordered lists that use
-
as the list marker. For example, the following is successfully tokenized:However, the tokenizer does not support ordered lists, which are an essential feature of Markdown. This includes lists using numeric markers followed by a period, such as:
Expected Behavior
The tokenizer should be able to recognize and generate tokens for both unordered and ordered lists, ensuring consistent handling of list structures. This includes:
1.
,2.
).Impact
Currently, ordered lists are entirely ignored or misinterpreted during tokenization. This limits the functionality and correctness of the Markdown parser, leading to incomplete rendering in downstream applications such as PDF generation or HTML rendering.
The text was updated successfully, but these errors were encountered: