public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Shane Liesegang <liesegang-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: How to tell an Inlines object from a table in a Lua filter?
Date: Mon, 23 May 2022 23:49:43 -0700 (PDT)	[thread overview]
Message-ID: <0a182969-9df6-4462-aae8-28f34d5b2e37n@googlegroups.com> (raw)
In-Reply-To: <84bdd685-384d-4fc4-bee5-75344028f42fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


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

I've figured out a workaround, but just wondering if there's a better way 
than diving into the metatables: 

~~~
function fix_table_strings(t)
  for k, v in pairs(t) do
    if type(v) == "table" then
      local metatable = getmetatable(v)
      if metatable ~= nil and metatable.__name == "Inlines" then
        t[k] = pandoc.utils.stringify(v)
      else
        fix_table_strings(t[k])
      end
    end
  end
end
~~~

On Tuesday, May 24, 2022 at 9:30:41 AM UTC+3 Shane Liesegang wrote:

> Is there a way to tell whether a given object is a pandoc.Inlines as 
> opposed to a plain Lua table? When I call `type(obj)` on it, it just 
> returns "table." I note that if I print it, it shows "Inlines:" instead of 
> "table:" but is there any smarter way to determine? 
>
> I see some code in the Lua filters example repository 
> <https://github.com/pandoc/lua-filters/blob/03c0fef0e56274ec9c958cdfe508a20618a1b623/scholarly-metadata/scholarly-metadata.lua#L45> 
> that does this kind of check, but I don't know if it's crucial to that code 
> or not, if something has changed recently, etc. 
>
> (My use case here is walking through my Meta object and building something 
> that will get passed to different functions -- if it encounters a nested 
> table of data, I need to recurse, but if it's an Inlines object, I want to 
> stringify it.) 
>
>

-- 
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/0a182969-9df6-4462-aae8-28f34d5b2e37n%40googlegroups.com.

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

  parent reply	other threads:[~2022-05-24  6:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-24  6:30 Shane Liesegang
     [not found] ` <84bdd685-384d-4fc4-bee5-75344028f42fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-05-24  6:49   ` Shane Liesegang [this message]
     [not found]     ` <0a182969-9df6-4462-aae8-28f34d5b2e37n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-05-24  9:13       ` 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=0a182969-9df6-4462-aae8-28f34d5b2e37n@googlegroups.com \
    --to=liesegang-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).