I think I will use the files in the test directory. I'll pass them through pandoc first without a filter, then with a filter that does nothing, to ensure the AST is the same.

I'm assuming files that end with .native are the produced AST representations for each file, and the following folders don't have native files:

* Tests - contains the Haskell test runner

* lua

* ipynb

* media

1. What are the writer.* files?

2. What's in docx/golden?

Thanks in advance.

On Tuesday, November 24, 2020 at 4:07:27 AM UTC+2 christi...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org wrote:

In pandoc repo, under test dir, there’sa lot of native files. You can then use pandoc to convert them to JSON as a starting point.

Also, you could consider using other filter framework as a starting point. Not as something you use in the long term, but as you first develop your framework as part of validation phase.

One example would be panflute in Python. You can feed in JSON to it using convert_text. And if it fail to parse it, it will emits useful debug information, Eg telling you a certain element is expecting a Block but get an Inline instead.

On Sunday, November 22, 2020 at 1:48:26 PM UTC-8 spit...@gmail.com wrote:

I am trying to develop a .NET package that can be used for writing JSON-based input filters. Can anyone recommend a sample document that I can use to see that the JSON is being parsed correctly?

Alternatively, is there a set of tests which filters have to pass?

--
You received this message because you are subscribed to a topic in the Google Groups "pandoc-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/pandoc-discuss/gQRR9qat9Zw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/b16cdc3d-2be8-4ca5-92c4-137a53834b26n%40googlegroups.com.