[BUG] {{DATE}} isn't scoped for choices nested under macro when set to variable #2242

Activity

1. aarontcannon

   added

   bugSomething isn't workingSomething isn't working

   on Oct 16, 2026
2. aarontcannon

   changed the title [-][BUG] {{DATE}} isn't scoped for choices nested under macro[/-] [+][BUG] {{DATE}} isn't scoped for choices nested under macro when set to variable[/+] on Oct 16, 2026
3. chhoumann

   added 2 commits that reference this issue on Oct 16, 2026

   test(date): cover per-choice Which day in macros and executeChoice

   ...

   f10402b

   fix(date): scope Which day to the choice that sets it

   ...

   890a61e
4. chhoumann

   linked a pull request that will close this issuefix(date): scope Which day to the choice that sets it #2243on Oct 16, 2026
5. chhoumann

   closed this as completedin #2243on Oct 16, 2026
6. chhoumann commented on Oct 16, 2026

   

   chhoumann

   on Oct 16, 2026

   Owner

   More actions

   Hey @aarontcannon! Thanks for the report, and for the clear repro steps. They made this easy to pin down. I could reproduce it, and it's fixed in #2243, which will ship in the next QuickAdd release.

   QuickAdd remembered the day the first Template picked, and kept using it for the rest of the macro. So your second Template, set to tomorrow, got yesterday's date too, and both tried to write the same file. Now a choice's Which day only applies to that choice and to anything it runs itself. A Macro's own Which day still applies to every choice inside it.

   I tested it in Obsidian with your setup: a template with just {{DATE}}, a script that sets yesterday and tomorrow, and a macro that runs the template twice, once with each variable. Before the fix, it created one file. After the fix, it creates two, each named and filled with its own date.

   About executeChoice(). Scripts are covered too. Each executeChoice() call now gets its own day, whether it comes from options.date or from a date variable the choice reads, and that day no longer carries over to later steps in the macro. One part I couldn't reproduce: repeated calls with different options.date values already worked for me when the called Template's Which day was left on Today. If your script still creates only one file after you update, please paste it here.

   Until the release is out, you can get both files from a script. Leave the template's Which day on Today, and pass the date in each call:

   module.exports = async ({ quickAddApi }) => {
   	const yesterday = moment().subtract(1, "day").format("YYYY-MM-DD");
   	const tomorrow = moment().add(1, "day").format("YYYY-MM-DD");
   	await quickAddApi.executeChoice("Your template", {}, { date: yesterday });
   	await quickAddApi.executeChoice("Your template", {}, { date: tomorrow });
   };

   Replace Your template with your Template choice's name. Let me know if anything still acts up after you update!
7. philoserf

   added a commit that references this issue on Oct 16, 2026

   fix(date): scope Which day to the choice that sets it (chhoumann#2243)

   ...

   487496a