Code Monkey home page Code Monkey logo

logseq13-full-house-plugin's People

Contributors

dsarman avatar semantic-release-bot avatar stdword avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

logseq13-full-house-plugin's Issues

Render result has duplicate blocks.

Template

- #L/Feedback --> What's the feedback
  template:: FH-L-Feedback
  template-including-parent:: true
  is-a:: [[Database/Feedback]]
  area:: ``[c.args.area]``
  team:: ``[c.args.team]``
  to-who:: [[@WHO]]
	- Context
	- What's Good
	- What's Bad
	- Follow up actions

Render with
{{renderer :template, FH-L-Feedback,  :area "Me@Personal", :team "Me@Personal", :delay-until-rendered}}

Result

- #L/Feedback --> What's the feedback
  is-a:: [[Database/Feedback]]
  area:: [[Me@Personal]]
  team:: [[Me@Personal]]
  to-who:: [[@WHO]]
	- Context
	- What's Good
	- What's Bad
	- Follow up actions
	- Context
	- What's Good
	- What's Bad
	- Follow up actions

Subblock render twice.

Logseq version: 0.9.15, Plugin version: 3.0.0

Included template renders `template-list-as` property

When my template consists of a bunch of await include('…') statements, those subtemplates, while rendered, include the template-list-as property.

Desired state: template-list-as is being skipped like template or template-including-parent properties.

Render template loss inner block

Template with template-including-parent:: true

- template:: simple
  template-including-parent:: true
  comment:: The most simple template
	- Hello, Logseq!
		- inner block

Render with
{{renderer :template, simple}}

Result

- comment:: The most simple template
	- Hello, Logseq!
		- inner block

Template without template-including-parent:: true

- template:: simple
  comment:: The most simple template
	- Hello, Logseq!
		- inner block
		
Render with
{{renderer :template, simple}}

Result

- Hello, Logseq!

The inner block is missing.

Logseq version : 0.9.15, Plugin version: 3.0.0

Template Inheritance

Idea: the easy way of declare different sets of arg-props for the same template (eg Glass Card)

reference: #9 (reply in thread)

If you are waiting for this task:

  • Please add πŸ‘€ reaction so I can prioritise it over other features
  • You can subscribe for notifications on this issue

Date language

I write my notes in pt-BR. Is there a configuration to set weekday aliases to be in pt-BR instead of en? For example, Terça-feira instead of Tuesday?

Is a setting in the plugin or in Logseq?

Page-ref macro arg confused with other args

@Gitbreast reported:

It seems to be sensitive to the order of arguments. In my test, the first argument seems always be considered as a page name, even if I specified all the arguments using -.

This is true:

Page-ref arg was introduced to easily switch c.page context variable to render templates for another page. But with introduction of template args things start to confuse.

As of for now page arg must be specified (with Β«β€”Β» to skip or in full page-ref form) every time you want to send an argument to template. This task is to implement a ways to get off the ambiguity.

[UI] Select template from a list

Currently when adding full house template command, need to type template name manually.
It will be great if list of templates can be shown, similar to regular templates behavior.

*Current workaround: adding command for each template in config.edn with full render full house template name. (Or using text expander)

Thanks for this great plugin! πŸ™

How should I use the new syntax

I see the new syntax here. But "Use Β«[Β» and Β«]Β» to call" seems not work. I just change the js code base on old template like this.

image

Rendering is space sensitive

@Gitbreast reported:

Are all macros "space sensitive"? I found if no space between a comma and an argument, the macro would not be rendered.

This is a bug: I definitely stands on importance to be space-independent and user friendly as much as possible.

Expected: all these renderings should have the same result:
{{renderer :template, wiki,Logseq}}
{{renderer :template, wiki, Logseq}}
{{renderer :template, wiki, Logseq}}

Any way to render but keep the original block contents?

Looking for a quick way to insert a wiki link using the current page name, first I consider logseq-powerblocks-plugin then cannibalox in forum recommend this.Then I experience this powerful plugin, it deal with the variable such as page name perfectly.

But while I use it in page property block, I realize it renders after clearing the original content of the block. That means it can't be use in a block that has any content. I think this would cause a big limit to its powerful feature.

So I think is it any way to add the template content but do not clear or replace the original content, just like logseq-powerblocks-plugin?

Discussion: https://discuss.logseq.com/t/any-way-to-get-variables-value-in-custom-commands/15994/1

Macro style (width) changed after loading plugin

Thanks for your awesome job, it really helps me a lot in inserting template. Today I try to use the macro function and found the style(width) of {{iframe }} is not consist, whose commands I used is same as #1.

:macros {
 "iframe" "<iframe src='$1' style='height:320px'></iframe>"
}

And here is the means to reproduce:

Logseq_462

I found that the plugin is not including the css code, and I have no idea how to avoid rendering this block. So I try to use another alternative solution as follows:

<iframe src = '' style= 'height:320px'></iframe>
template:: iframe-full-house

It works as well. Thus the priority of issue is not much high. I'm looking forward to fix it one day. Thanks your job again.

(Windows 11; [email protected]; [email protected])

Make copy-paste of a rendered template easy

I have created a template that works perfectly. Basically it renders a text substituting a variable with the corresponding value. I want to copy the generated text to the clipboard, but when i try to select the text i want to copy, the erendered text turns into "{{renderer :template-view, InnBoK type prompt template}}". Is there a way i can copy the rendered text to the clipboard?

Is it possible to use it as a journal template?

First, thanks for developing such a cool plugin.

I use page like [[2023/W1]] as periodical retrospective page. For each daily journal, it will have properties like "week" link to this page.

For example, the content of journal 2023-03-19.md should be like:

<!-- page properties -->
year:: [[2023]]
week:: [[2023/W12]]

<!-- journal data -->

After I see this plugin, I wonder if I can use it to automatically generate my daily journal. For now, I have tried the following thing but fail.

  • Create a template like the following:
- ## Journal template date
  template:: journal-date
	- year:: ``{ ref(date.from(c.page.name).format('YYYY')) }``
	  week:: ``{ ref(date.from(c.page.name).format('YYYY/[W]w')) }``
  • Put the line {{renderer :template, journal-date}} in my journal template.

The plugin rendered the macro, so I could not use it to generate my journal.

How to call day.js function

I have template like this:

Today Work [[``{ date.from(c.page.name).year() }``-W``{ date.from(c.page.name).week() }``]]

But I need call day.js isoweek. How can I do? Thanks!

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.