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
Also: I'm not clear about the significance of multiple table bodies. Can you give an example of a rendered table with multiple bodies, so I can see what it would be used for? (I know that HTML and our AST allow this.)
Our test suite uses an example from MDN to test handling of multiple bodies. I don't particularly like these tables: most of the times those table should have an additional column instead, or be presented as separate tables. So I'm ok with not supporting them for now.
The updated parser follows rst interpretation of two consecutive row separators: it treats the above as a single table with three rows, where the second row is empty. I hadn't realize that we changed parsing behavior in this case.
An image search for "rowgroup tables" yields a number of tables that, I have to admit, look like legitimate use cases for this feature. Example taken from this question.
This is a proposal to add support for multiple table bodies by treating two consecutive row separators as table body delimiter.
E.g., this table
would be parsed to
Note that the bodies can have header rows, but the first head separator (
+===+
) always marks the head of the full table.The text was updated successfully, but these errors were encountered: