[BUG] Template variables not processed?
See original GitHub issueMaybe I m doing something wrong here (new to the plugin).
I created a “Template” Quick add and selected the template from the list (using the Obsidian core plugin, NOT templater).
However, template variables like {{title}}
are not being processed.
When I run the Obisidian command to add the template to the current note, it works fine
To Reproduce Steps to reproduce the behavior:
- Create a template (with core plugin) using variable
{{title}}
somewhere in the template - Create Quick Add Choice of type “Template”
- Select the template created in 1.
- Run the Quick Add command
Expected behavior
New note gets created using the specified template. {{title}}
variable gets replaced with actual value.
Actual behavior
New note gets created, however {{title}}
does not get replaced.
Issue Analytics
- State:
- Created a year ago
- Reactions:9
- Comments:6 (1 by maintainers)
Top Results From Across the Web
[Bug] Template Variables Not Working if Field Type is a ...
The template doesn't work when the field of a variable is a number. When writing a query in a template, I use a...
Read more >Typing $ to create or list template variables does not work - Jira
Edit or Create a template using the new editor;; Insert a variable into the template by: Clicking the + button on the top...
Read more >variables no longer working in provisioning {a bug?}
I've been successfully provisioning machines for quite a few years using VARIABLES within my provisioning templates. I've just moved from LDMS 9.0 to...
Read more >82292 – Code template variables not working - Bugs - Eclipse
From CDT 2.1 1. In a project, create a new file ("test.c"). 2. Type "com" then Ctrl-Space, to invoke the comment block for...
Read more >YAML pipeline - Variables in template aren't passed down to ...
Hi there, This is an expected behavior. The template in steps will not be processed at compile time. In a pipeline, template expression ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi everyone, thank you for contributing to the discussion here!
This isn’t a bug. It is intended. I can see, however, that this is something which could contribute to the experience of using QA.
There are two reasons why I haven’t implemented this already:
title
is an issue. The reason it works with<% tp.file.title %>
(Templater) is because that is done after creating the note. QuickAdd tries to do things before actually creating the note.As a compromise, I have allowed all format syntax to be lowercase as of #326, or v0.7.0. Meaning,
{{DATE}}
is now equivalent to{{date}}
.That leaves
{{time}}
and{{title}}
. As @Amparose mentions, you can use{{DATE:YYYY/MM/DD}}
and{{DATE:HH:mm}}
(or lowercase now) for{{date}}
and{{time}}
, respectively. This was the indented use from the start.I may implement
{{title}}
at some later date. Please track #327 for this.Again, thank you everyone for contributing! It is very much appreciated.
Just wanted to add that this also doesn’t work with the other template variables:
{{date}}
{{time}}
.