public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Markdown in JSON (was: Parse metadata in defaults files as Markdown?)
Date: Mon, 02 Oct 2023 21:08:36 +0200	[thread overview]
Message-ID: <87edicolz7.fsf@zeitkraut.de> (raw)
In-Reply-To: <CADAJKhC6T=UHG49Rtd40nYsQFgfMxuiwyjqK3A+9CQ0QwjYXzQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>


BPJ <melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> how and when does `pandoc.json.decode()` parse its argument into AST
> elements?

Decoding to AST elements if possible is the default, but that can be
disabled by passing `false` as the second argument:

     > pandoc.json.decode('{"t":"Str", "c":"Hello"}')
     Str "Hello"
     > type(pandoc.json.decode('{"t":"Str", "c":"Hello"}'))
     userdata

     > pandoc.json.decode('{"t":"Str", "c":"Hello"}', false)
     table: 0xc742c60
     > type(pandoc.json.decode('{"t":"Str", "c":"Hello"}', false))
     table

The "how" is rather simple: the function tries to parse the input as
Inline, Block, Pandoc, Inlines, and Blocks, in that order. If one of
those attempts succeeds, then the respective AST element is returned.
Otherwise it falls back to returning the value as a plain Lua object.


-- 
Albert Krewinkel
GPG: 8eed e3e2 e8c5 6f18 81fe  e836 388d c0b2 1f63 1124


  parent reply	other threads:[~2023-10-02 19:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-28 16:20 Parse metadata in defaults files as Markdown? Martin Post
     [not found] ` <a4843b38-f508-4d55-8dd0-35136f401bd1n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-09-29 18:37   ` Albert Krewinkel
     [not found]     ` <87r0mgof6d.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2023-09-30  9:03       ` Martin Post
2023-10-01 10:50       ` Markdown in JSON (was: Parse metadata in defaults files as Markdown?) BPJ
     [not found]         ` <CADAJKhC6T=UHG49Rtd40nYsQFgfMxuiwyjqK3A+9CQ0QwjYXzQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-10-02 19:08           ` Albert Krewinkel [this message]
     [not found]             ` <87edicolz7.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2023-10-05 10:14               ` BPJ

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=87edicolz7.fsf@zeitkraut.de \
    --to=albert+pandoc-9eawchwdxg8hfhg+jk9f0w@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).