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
I would like to inquire about the possibility to increase backward- and forward-compatibility in pandoc-types. For example, in pandoc-types 1.21, changes to the AST has broken the way a few filters work. The new Table block element is not crucial for many filters (e.g. pandoc-plot or pandoc-include-code), so the breakage is artificial.
I propose that the next time the AST is changed, a new block element, Unknown, be added. Then, the function toJSONFilter could be changed so that instead of throwing an error on incompatible pandoc-types version, the Unknown block element could be used as a placeholder for AST blocks that are not decoded appropriately.
This would allow for filters to be compatible with a wider range of pandoc-types and pandoc versions.
Let me know what you think.
The text was updated successfully, but these errors were encountered:
Hello,
I would like to inquire about the possibility to increase backward- and forward-compatibility in pandoc-types. For example, in
pandoc-types 1.21
, changes to the AST has broken the way a few filters work. The newTable
block element is not crucial for many filters (e.g. pandoc-plot or pandoc-include-code), so the breakage is artificial.I propose that the next time the AST is changed, a new block element,
Unknown
, be added. Then, the functiontoJSONFilter
could be changed so that instead of throwing an error on incompatiblepandoc-types
version, theUnknown
block element could be used as a placeholder for AST blocks that are not decoded appropriately.This would allow for filters to be compatible with a wider range of
pandoc-types
andpandoc
versions.Let me know what you think.
The text was updated successfully, but these errors were encountered: