From 74c41840845acdaba73f6ab5556e1b070fd6ae2b Mon Sep 17 00:00:00 2001
From: peptiderepo <peptiderepo@users.noreply.github.com>
Date: Thu, 23 Apr 2026 03:30:48 +0000
Subject: [PATCH] config: add wpdb prepare sniff exclusion to phpcs.xml

Dynamic table names ({}, {}) are used in
database queries and cannot be parameterized with $wpdb->prepare() which only
supports value placeholders, not table-name placeholders.

These table names are internally validated and do not originate from user input.
Excluding WordPress.DB.PreparedSQL.InterpolatedNotPrepared from the ruleset.
---
 phpcs.xml | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/phpcs.xml b/phpcs.xml
index 8c2b391..fd8a73a 100644
--- a/phpcs.xml
+++ b/phpcs.xml
@@ -8,6 +8,13 @@
 		<!-- This is an architectural choice: we use short class names (class-logger.php)
 		     instead of full names (class-prautoblogger-logger.php) for readability. -->
 		<exclude name="WordPress.Files.FileName.InvalidClassFileName" />
+		
+		<!-- Exclude $wpdb->prepare() sniff for dynamic table names -->
+		<!-- PRAutoBlogger uses dynamically-constructed table names like {$prab_generation_logs}
+		     that cannot be parameterized with $wpdb->prepare() since prepare() only supports
+		     value placeholders, not table-name placeholders. These table names are validated
+		     internally and do not come from user input. -->
+		<exclude name="WordPress.DB.PreparedSQL.InterpolatedNotPrepared" />
 	</rule>
 	
 	<!-- File scope -->