peanball / logseq-dynamic-lookup Goto Github PK

My case #1: I want to check if a property exists, without using fallbackTemplate.

With a mustache-like template language it can looks like:

{{renderer :lookup, page, :alias:description, "{{#alias}} ({{alias}}){{/alias}}: {{description}}"}}

And specifing list of properties now looks unnecessary:

{{renderer :lookup, page, "{{#alias}} ({{alias}}){{/alias}}: {{description}}"}}

My case #2: Use page name

With a template language we can save a page meta-info as a default context:

{{renderer :lookup, page, "[[{{ page.name }}]] {{#page.props.alias}} ({{page.props.alias}}){{/page.props.alias}}: {{page.props.description}}"}}

Proposal:

{{renderer :lookup, PAGE, prop1:prop2:prop3, <a href="$prop1">$prop2</a>, $prop3}}

instead of just putting the property value as $value.

I think it could be useful to look for properties and content of blocks too.

In particular I'm referring to:

1. the parent block if any (maybe fallback to current page title and properties otherwise?)
2. Previous/next sibling block

An use case for 1. could be:

You are in a page/block about an Author and you want to use a "New Book" template to create a Book that has page title/block content as the value of author:: property:

- Name Surname
  - Title of the book created with a template
    author:: Name Surname