From 83b25c95fb44aa419b1c88ecb604b03b46546d5a Mon Sep 17 00:00:00 2001
From: Ferran Basora <ferran.basora@factorial.co>
Date: Mon, 1 Jun 2026 20:19:43 +0200
Subject: [PATCH] Resolve {{ index }} in a plain request (fixes #186)

Seed `index` with the iteration counter when building each iteration's
context, so `{{ index }}` resolves in a plain request instead of panicking
with "Unknown 'index' variable" in strict mode (or interpolating to an empty
string under --relaxed-interpolations).

with_items / csv / file / range expansions still override `index` with the
item's list position at execute time, so their semantics are unchanged.
---
 src/benchmark.rs | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/src/benchmark.rs b/src/benchmark.rs
index f3c10e1..6587d1b 100644
--- a/src/benchmark.rs
+++ b/src/benchmark.rs
@@ -39,6 +39,8 @@ async fn run_iteration(benchmark: Arc<Benchmark>, pool: Pool, config: Arc<Config
 
   context.insert("iteration".to_string(), json!(iteration.to_string()));
   context.insert("base".to_string(), json!(config.base.to_string()));
+  // Default `index` to the iteration counter so `{{ index }}` resolves in a plain request; with_items expansions override it with the item position at execute time.
+  context.insert("index".to_string(), json!(iteration));
 
   for item in benchmark.iter() {
     item.execute(&mut context, &mut reports, &pool, &config).await;