Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backward- and forward-compatibility #73

Open
LaurentRDC opened this issue Jul 13, 2020 · 3 comments
Open

Backward- and forward-compatibility #73

LaurentRDC opened this issue Jul 13, 2020 · 3 comments

Comments

@LaurentRDC
Copy link

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

@jgm
Copy link
Owner

jgm commented Jul 13, 2020

Interesting idea. I don't really know what I think. Probably this should be raised for discussion on pandoc-discuss.

@LaurentRDC
Copy link
Author

This topic is visible here.

@tarleb
Copy link
Contributor

tarleb commented Oct 8, 2020

Orthogonal to the solution proposed here, but aiming to solve the same problem: ast-migrator.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants