From dbfc50cee112b2b9f06ab692356871c2a4efa746 Mon Sep 17 00:00:00 2001
From: peptiderepo <peptiderepo@users.noreply.github.com>
Date: Tue, 23 Jun 2026 05:19:43 +0000
Subject: [PATCH] style: move phpcs:ignore to echo output line for PHPCS
 compliance

EscapeOutput sniff fires on the argument line of multi-line printf, not
the call site. Collapse to single-line echo so the phpcs:ignore inline
comment covers the offending expression. No functional change.

Agent-Session: prcore-jsonld-remediation-20260623
---
 includes/frontend/class-pr-core-jsonld-article.php | 6 +-----
 1 file changed, 1 insertion(+), 5 deletions(-)

diff --git a/includes/frontend/class-pr-core-jsonld-article.php b/includes/frontend/class-pr-core-jsonld-article.php
index 4b1eb8d..dc116de 100644
--- a/includes/frontend/class-pr-core-jsonld-article.php
+++ b/includes/frontend/class-pr-core-jsonld-article.php
@@ -210,11 +210,7 @@ class PR_Core_Jsonld_Article {
 			JSON_UNESCAPED_SLASHES | JSON_UNESCAPED_UNICODE | JSON_PRETTY_PRINT
 		);
 		if ( false !== $json ) {
-			// phpcs:ignore WordPress.Security.EscapeOutput.OutputNotEscaped -- wp_json_encode() is the canonical JSON escape; no further escaping needed.
-			printf(
-				'<script type="application/ld+json">%s</script>' . "\n",
-				$json
-			);
+			echo '<script type="application/ld+json">' . $json . '</script>' . "\n"; // phpcs:ignore WordPress.Security.EscapeOutput.OutputNotEscaped -- wp_json_encode() already escapes for JSON context.
 		}
 	}