From cd6d7c5c1d4951cdf4b139ff725d6011537d9c5f Mon Sep 17 00:00:00 2001 From: Dan Draper Date: Sun, 18 Oct 2026 19:20:32 +1100 Subject: [PATCH] fix(eql): build the TextEq query fixture's input as a frame, so v4_types compiles on next #1257 added a TextEq query to the v4 query fixture with an FfiValue input, and #1259 removed FfiValue from v4_types.rs. Each passed on its own; merged together on next, the test file does not compile. The input is now frame("alice@example.com"), as every other query there is, and the fixture's bytes are unchanged. --- packages/eql/tests/encryption/tests/v4_types.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/eql/tests/encryption/tests/v4_types.rs b/packages/eql/tests/encryption/tests/v4_types.rs index a0c7685dd..176715456 100644 --- a/packages/eql/tests/encryption/tests/v4_types.rs +++ b/packages/eql/tests/encryption/tests/v4_types.rs @@ -973,7 +973,7 @@ async fn the_v4_query_fixture_is_what_the_dispatch_derives() { }, "email": { "plaintext": "alice@example.com", - "query": query("TextEq", "email", FfiValue::String("alice@example.com".into())).await, + "query": query("TextEq", "email", frame("alice@example.com")).await, }, }); let path =