public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Zev Spitz <spitzzev-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Sample documents for testing JSON filters
Date: Sat, 12 Dec 2020 12:26:11 -0800 (PST)	[thread overview]
Message-ID: <b16cdc3d-2be8-4ca5-92c4-137a53834b26n@googlegroups.com> (raw)
In-Reply-To: <f2c7aa8e-6bfe-4b9a-89e8-adbdcd1225a8n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 2011 bytes --]

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...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org 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 the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@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.

[-- Attachment #1.2: Type: text/html, Size: 2877 bytes --]

  parent reply	other threads:[~2020-12-12 20:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-22 21:48 Zev Spitz
     [not found] ` <5e4c5ac9-b24c-4d4e-a0b3-3a094c263555n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-11-23 18:15   ` John MacFarlane
2020-11-24  2:07   ` christi...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
     [not found]     ` <f2c7aa8e-6bfe-4b9a-89e8-adbdcd1225a8n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-12-12 20:26       ` Zev Spitz [this message]
     [not found]         ` <b16cdc3d-2be8-4ca5-92c4-137a53834b26n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-12-12 22:58           ` Kolen Cheung
2021-01-03 13:59             ` Zev Spitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b16cdc3d-2be8-4ca5-92c4-137a53834b26n@googlegroups.com \
    --to=spitzzev-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).