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
TABLE aligns ->error"constructing table not supported"TABLE_ROW->error"constructing table row not supported"TABLE_CELL->error"constructing table cell not supported"
It would be great if tables could be supported. Is there some problem? Perhaps I can help.
Also: this library will abort with an uncatchable runtime error, crashing any program that uses it, if you try to render a table node. That is not good behavior for a library. error should be used only in "should not happen" cases, i.e. for programming errors.
The text was updated successfully, but these errors were encountered:
Looking into this further, I notice that cmark-gfm lacks any good way to programatically construct the nodes provided by extensions. So, for example set_table_alignments is a static function in tables.c, not an exported function. Is there a reason for this?
jgm
added a commit
to jgm/pandoc
that referenced
this issue
Aug 8, 2017
We bypass the commonmark writer from cmark and construct our
own pipe tables, with better results. (Note also that cmark-gfm
currently doesn't support rendering table nodes; see
kivikakk/cmark-gfm-hs#3.)
Line 484 of CMarkGFM.hsc:
It would be great if tables could be supported. Is there some problem? Perhaps I can help.
Also: this library will abort with an uncatchable runtime error, crashing any program that uses it, if you try to render a table node. That is not good behavior for a library.
error
should be used only in "should not happen" cases, i.e. for programming errors.The text was updated successfully, but these errors were encountered: