[BUG] Placeholders from format syntax (e.g. : {{VALUE:fileName}}) generate a warning in Obsidian console.

[Elaws]

Describe the bug

In the QuickAdd.variables = {...} part of a .js file loaded by QuickAdd, fileName is a simple string.

The following template...

... generates the following warning in Obsidian console :

To Reproduce
Steps to reproduce the behavior in Obsidian:

1. Open Obsidian and create note template mentionned above.
2. Have a .js script loaded by Obsidian that outputs a string named fileName so you can use {{VALUE:fileName}} in your template.
3. See warning.

Expected behavior
No such warning.

Obsidian Debug Info (required for bug reports)
Please include the full Debug Info from Obsidian to help diagnose your environment:

• Open the Command Palette (Ctrl/Cmd+P).
• Run: Show debug info.
• Click: Copy to clipboard.
• Paste it below inside the code block.

PASTE DEBUG INFO HERE

Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

• Obsidian version: 1.13.4
• QuickAdd version: 2.21.0
• Operating system: Windows 11
• Debug info: Cf. screenshot above
• Other plugins enabled: [List any other plugins that might be relevant]
• Theme: Default

Console Logs

Cf. screenshot above.

[MelodyDuplaix]

You can wrap the quickadd placeholder syntax between quotation marks to prevent this warning by letting Obsidian know that it is a string.
Like this :

---
Title: "{{VALUE:fileName}}"
---

[Elaws]

You can wrap the quickadd placeholder syntax between quotation marks to prevent this warning by letting Obsidian know that it is a string. Like this :

---
Title: "{{VALUE:fileName}}"
---

Thanks : However, won't this interfere with Obsidian or QuickAdd's ability to recognize property type (number, boolean, lists, etc...) ?

[MelodyDuplaix]

Obsidian recognize string value by either just the value, or by the value between quotation marks, so no , it won't interfere with obsidian recognition. If you do the same for a number value, obsidian will display an error in the frontmatter ui because it will detect a string value in a property with number value, but it won't cause any other errors, neither warning in console (same for other properties types).
For quickadd, even if the value is number, quickadd will normally convert to the correct type (I made some tests, and it works for me.