[BUG] js quickadd String `replace`, `test` function and other manipulations assumes literal `{{VALUE}}`, not selection

[ces3001]

Describe the bug
Using js quickadd in the Capture Fromat:
where val = “{{VALUE}}”, val.replace function assumes literal {{VALUE}}, not selection, if grep matches something in the literal string ”{{VALUE}}”, otherwise leaves selection.
If you simply return val, it returns the selection.

To Reproduce

let v = "{{VALUE}}";
return v.replace(/[VWXYZwxyz]/g, '9');

will incorrectly return {{9ALUE}} as the V matches in {{VALUE}}.
{{VALUE}} seemingly doesn’t get replaced with the selected text, but is taken literally.

Whereas, omitting the V in the grep pattern:

let v = "{{VALUE}}";
return v.replace(/[WXYZwxyz]/g, '9');

This will do nothing, and correctly return the selected text (not {{VALUE}}), because /[WXYZwxyz]/g doesn’t match anything in the string {{VALUE}}.

Expected behavior
replace should use the replacement selection string. In the example above, depending on the selection.
If selection = VWA, then replaced with 99A, not {{9ALUE}}

Desktop (please complete the following information):

• OS: macOS
• Obsidian: Version 1.5.12
• QuickAdd 1.6.1

Additional context
I’m trying to implement a “Convert Phone to Link” function:

function convertPhoneNumberToLink(linkNumber) {
  // Remove all non-alphanumeric characters except +
  linkNumber = linkNumber.replace(/[^a-zA-Z0-9+]/g, '');

  // Replace letters with their corresponding numbers
linkNumber = linkNumber.replace(/[ABCabc]/g, '2');
linkNumber = linkNumber.replace(/[DEFdef]/g, '3');
linkNumber = linkNumber.replace(/[GHIghi]/g, '4');
linkNumber = linkNumber.replace(/[JKLjkl]/g, '5');
linkNumber = linkNumber.replace(/[MNOmno]/g, '6');
linkNumber = linkNumber.replace(/[PQRSpqrs]/g, '7');
linkNumber = linkNumber.replace(/[TUVtuv]/g, '8');
linkNumber = linkNumber.replace(/[WXYZwxyz]/g, '9');

  return `tel:${linkNumber}`
}
return `[{{VALUE}}](${convertPhoneNumberToLink("{{VALUE}}")})`;

This will always return [ACTUAL PHONE NUMBER SELECTED](tel:82583) because 82582 is VALUE on the numeric keypad.

[ces3001]

ps. replacing the last line with

let v = "{{VALUE}}";
return `[${v}](${convertPhoneNumberToLink(v)})`;

Still gives the wrong result. [+1-800-CALL-APPL](tel:+182583) it doesn’t change the bug.

[ces3001]

Please excuse the multiple follow-ups. It seems to me that QuickAdd isn’t replacing the {{VALUE}} string in the code before the execution of the javascript, but only replacing it after in the javascript's output.

So it’s perhaps a bug, perhaps a design decision. For now, I guess, we request it as feature -> #483

[chhoumann]

Triage update (2026-02-22): I can still reproduce this on current QuickAdd 2.11.0 in the dev vault.

Repro used:

1. Source note content: VWA (selected in editor)
2. Capture format:

let v = "{{VALUE}}";
return v.replace(/[VWXYZwxyz]/g, "9");

3. Run capture command

Actual output inserted: {{9ALUE}}
Expected output: 99A

No runtime errors are raised in dev:errors.

Likely root cause: formatter execution order in CompleteFormatter.format currently runs inline js quickadd blocks before replaceValueInString, so the script sees the literal token and can mutate it before {{VALUE}} substitution occurs.

[chhoumann]

Implemented as a docs clarification (no runtime behavior change) on branch 672-bug-js-quickadd-string-replace-test-function-and-other-manipulations-assumes-literal-value-not-selection.

What was updated:

• Inline scripts docs now explicitly explain execution order and why "{{VALUE}}" inside js quickadd is literal token text during script execution.
• Added API-first examples using this.quickAddApi.inputPrompt(...) + this.variables for transformation workflows (including phone-to-link).
• Added cross-references from Format Syntax and Capture docs so users are directed to the correct pattern.

Commit: eea9dfd

I will close this issue after the docs change is merged.

[chhoumann]

Thanks again for the detailed report and all the follow-ups here. The examples were very helpful.

I confirmed the behavior on current QuickAdd: inside an inline js quickadd block, "{{VALUE}}" is treated as literal token text at script execution time. So if the script mutates that string (for example with .replace()), it can mutate the literal token ({{VALUE}}) before the normal {{VALUE}} substitution phase runs.

So in practice:

• {{VALUE}} is great for formatter/template substitution
• for transformations inside inline JS, the recommended path is to read input directly via the QuickAdd API (or read editor selection directly), then transform that value

For your phone-link use case, this pattern should be reliable:

```js quickadd
function convertPhoneNumberToLink(linkNumber) {
  linkNumber = linkNumber.replace(/[^a-zA-Z0-9+]/g, "");
  linkNumber = linkNumber.replace(/[ABCabc]/g, "2");
  linkNumber = linkNumber.replace(/[DEFdef]/g, "3");
  linkNumber = linkNumber.replace(/[GHIghi]/g, "4");
  linkNumber = linkNumber.replace(/[JKLjkl]/g, "5");
  linkNumber = linkNumber.replace(/[MNOmno]/g, "6");
  linkNumber = linkNumber.replace(/[PQRSpqrs]/g, "7");
  linkNumber = linkNumber.replace(/[TUVtuv]/g, "8");
  linkNumber = linkNumber.replace(/[WXYZwxyz]/g, "9");
  return `tel:${linkNumber}`;
}

const view = this.app.workspace.getActiveViewOfType(this.obsidian.MarkdownView);
const selected = view?.editor?.getSelection()?.trim();
const raw = selected || await this.quickAddApi.inputPrompt("Phone number");
if (!raw) return "";

return `[${raw}](${convertPhoneNumberToLink(raw)})`;
```

I’ve also prepared docs updates so this behavior and workaround are clearer in the Inline Scripts / Format Syntax / Capture docs.

Really appreciate you taking the time to write this up so thoroughly.

[github-actions]

🎉 This issue has been resolved in version 2.12.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀