Summary
Currently, Claymore uses regex-based pattern matching to replace placeholders in JSON (i.e,. $string[8], $task.ResponseBody.token). While this works for basic cases, it quickly becomes difficult to maintain, extend, and debug. We should explore integrating with a templating engine to handle dynamic content in a structured way.
-- Regex replacements can become error-prone for nested or complex placeholders
-- Adding new templating features requires writing more custom regex logic
-- Regex lacks readability for complex more advanced dynamic expressions
Proposed Solution
Replace the current regex based templating with a templating engine like Scriban etc.
Provide claymore users with a way to embed templates in their JSON scripts.
Summary
Currently, Claymore uses regex-based pattern matching to replace placeholders in JSON (i.e,.
$string[8],$task.ResponseBody.token). While this works for basic cases, it quickly becomes difficult to maintain, extend, and debug. We should explore integrating with a templating engine to handle dynamic content in a structured way.-- Regex replacements can become error-prone for nested or complex placeholders
-- Adding new templating features requires writing more custom regex logic
-- Regex lacks readability for complex more advanced dynamic expressions
Proposed Solution
Replace the current regex based templating with a templating engine like Scriban etc.
Provide claymore users with a way to embed templates in their JSON scripts.