From 9ff792cf895f0138d1c85b83c5925178f5c42ccc Mon Sep 17 00:00:00 2001
From: gogdzl <diego.rodrigues@automattic.com>
Date: Tue, 17 Sep 2024 13:26:47 -0700
Subject: [PATCH 1/4] Add documentation for WordPress.PHP.DevelopmentFunctions

---
 .../Docs/PHP/DevelopmentFunctionsStandard.xml | 44 +++++++++++++++++++
 1 file changed, 44 insertions(+)
 create mode 100644 WordPress/Docs/PHP/DevelopmentFunctionsStandard.xml

diff --git a/WordPress/Docs/PHP/DevelopmentFunctionsStandard.xml b/WordPress/Docs/PHP/DevelopmentFunctionsStandard.xml
new file mode 100644
index 0000000000..a4761201f6
--- /dev/null
+++ b/WordPress/Docs/PHP/DevelopmentFunctionsStandard.xml
@@ -0,0 +1,44 @@
+<?xml version="1.0"?>
+<documentation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+    xsi:noNamespaceSchemaLocation="https://phpcsstandards.github.io/PHPCSDevTools/phpcsdocs.xsd"
+    title="Development Functions"
+    >
+    <standard>
+    <![CDATA[
+    Debug code should not normally be used in production.
+
+    Typically, this rule verifies if function calls to the PHP native `error_log()`, `var_dump()`, `var_export()`, `print_r()`, `trigger_error()`, `set_error_handler()`, `debug_backtrace`, `debug_print_backtrace` and `wp_debug_backtrace_summary()` functions are present in the code.
+    ]]>
+    </standard>
+    <code_comparison>
+        <code title="Valid: (Not) using var_dump().">
+        <![CDATA[
+// var_dump() should not be used.
+        ]]>
+        </code>
+        <code title="Invalid: Calling the PHP native `var_dump()` function.">
+        <![CDATA[
+<em>var_dump( $bar );</em>
+        ]]>
+        </code>
+    </code_comparison>
+    <standard>
+    <![CDATA[
+    Please refrain from using functions that can lead to full path disclosure.
+
+    Typically, this rule verifies if function calls to the PHP native `error_reporting()` and `phpinfo()` functions are present in the code.
+    ]]>
+    </standard>
+    <code_comparison>
+        <code title="Valid: (Not) using `phpinfo()`.">
+        <![CDATA[
+// php_info() should not be used.
+        ]]>
+        </code>
+        <code title="Invalid: Calling the PHP native `phpinfo()` function.">
+        <![CDATA[
+<em>phpinfo();</em>
+        ]]>
+        </code>
+    </code_comparison>
+</documentation>

From 0ea73de56d4ce1ae5fbef720488fc71fcb412b26 Mon Sep 17 00:00:00 2001
From: Rodrigo Primo <rodrigosprimo@gmail.com>
Date: Mon, 2 Feb 2026 16:27:46 -0300
Subject: [PATCH 2/4] Apply suggestions from PR review

- Change standard descriptions to be more direct.
- Remove function lists from standard descriptions.
- Fix "(Not)" in titles to "Not using...".
- Make titles and comments more generic.
- Fix typo `php_info()` to `phpinfo()`.
- Use "full path disclosure" consistently.
---
 .../Docs/PHP/DevelopmentFunctionsStandard.xml | 20 ++++++++-----------
 1 file changed, 8 insertions(+), 12 deletions(-)

diff --git a/WordPress/Docs/PHP/DevelopmentFunctionsStandard.xml b/WordPress/Docs/PHP/DevelopmentFunctionsStandard.xml
index a4761201f6..1413b6d408 100644
--- a/WordPress/Docs/PHP/DevelopmentFunctionsStandard.xml
+++ b/WordPress/Docs/PHP/DevelopmentFunctionsStandard.xml
@@ -5,18 +5,16 @@
     >
     <standard>
     <![CDATA[
-    Debug code should not normally be used in production.
-
-    Typically, this rule verifies if function calls to the PHP native `error_log()`, `var_dump()`, `var_export()`, `print_r()`, `trigger_error()`, `set_error_handler()`, `debug_backtrace`, `debug_print_backtrace` and `wp_debug_backtrace_summary()` functions are present in the code.
+    Debug functions should not be used in production code.
     ]]>
     </standard>
     <code_comparison>
-        <code title="Valid: (Not) using var_dump().">
+        <code title="Valid: Not using debug functions.">
         <![CDATA[
-// var_dump() should not be used.
+// Code without debug functions.
         ]]>
         </code>
-        <code title="Invalid: Calling the PHP native `var_dump()` function.">
+        <code title="Invalid: Calling a debug function.">
         <![CDATA[
 <em>var_dump( $bar );</em>
         ]]>
@@ -24,18 +22,16 @@
     </code_comparison>
     <standard>
     <![CDATA[
-    Please refrain from using functions that can lead to full path disclosure.
-
-    Typically, this rule verifies if function calls to the PHP native `error_reporting()` and `phpinfo()` functions are present in the code.
+    Functions that can lead to full path disclosure should not be used.
     ]]>
     </standard>
     <code_comparison>
-        <code title="Valid: (Not) using `phpinfo()`.">
+        <code title="Valid: Not using functions that can lead to full path disclosure.">
         <![CDATA[
-// php_info() should not be used.
+// No full path disclosure functions.
         ]]>
         </code>
-        <code title="Invalid: Calling the PHP native `phpinfo()` function.">
+        <code title="Invalid: Using a function that can lead to full path disclosure.">
         <![CDATA[
 <em>phpinfo();</em>
         ]]>

From e5ecb4f57940c7072885832fdd9be4643bbd964b Mon Sep 17 00:00:00 2001
From: Rodrigo Primo <rodrigosprimo@gmail.com>
Date: Tue, 3 Feb 2026 10:55:45 -0300
Subject: [PATCH 3/4] Remove code comparisons and add example functions to
 standard descriptions

---
 .../Docs/PHP/DevelopmentFunctionsStandard.xml | 28 ++-----------------
 1 file changed, 2 insertions(+), 26 deletions(-)

diff --git a/WordPress/Docs/PHP/DevelopmentFunctionsStandard.xml b/WordPress/Docs/PHP/DevelopmentFunctionsStandard.xml
index 1413b6d408..89c7a4ea1d 100644
--- a/WordPress/Docs/PHP/DevelopmentFunctionsStandard.xml
+++ b/WordPress/Docs/PHP/DevelopmentFunctionsStandard.xml
@@ -5,36 +5,12 @@
     >
     <standard>
     <![CDATA[
-    Debug functions should not be used in production code.
+    Debug functions, like var_dump() and print_r(), should not be used in production code.
     ]]>
     </standard>
-    <code_comparison>
-        <code title="Valid: Not using debug functions.">
-        <![CDATA[
-// Code without debug functions.
-        ]]>
-        </code>
-        <code title="Invalid: Calling a debug function.">
-        <![CDATA[
-<em>var_dump( $bar );</em>
-        ]]>
-        </code>
-    </code_comparison>
     <standard>
     <![CDATA[
-    Functions that can lead to full path disclosure should not be used.
+    Functions that can lead to full path disclosure, like phpinfo(), should not be used.
     ]]>
     </standard>
-    <code_comparison>
-        <code title="Valid: Not using functions that can lead to full path disclosure.">
-        <![CDATA[
-// No full path disclosure functions.
-        ]]>
-        </code>
-        <code title="Invalid: Using a function that can lead to full path disclosure.">
-        <![CDATA[
-<em>phpinfo();</em>
-        ]]>
-        </code>
-    </code_comparison>
 </documentation>

From 7be82d25a74b135cea0fee09f0aabcca84f49aee Mon Sep 17 00:00:00 2001
From: Rodrigo Primo <rodrigosprimo@gmail.com>
Date: Tue, 3 Feb 2026 11:09:48 -0300
Subject: [PATCH 4/4] Merge standard blocks into a single block

---
 WordPress/Docs/PHP/DevelopmentFunctionsStandard.xml | 7 +------
 1 file changed, 1 insertion(+), 6 deletions(-)

diff --git a/WordPress/Docs/PHP/DevelopmentFunctionsStandard.xml b/WordPress/Docs/PHP/DevelopmentFunctionsStandard.xml
index 89c7a4ea1d..625d86c435 100644
--- a/WordPress/Docs/PHP/DevelopmentFunctionsStandard.xml
+++ b/WordPress/Docs/PHP/DevelopmentFunctionsStandard.xml
@@ -5,12 +5,7 @@
     >
     <standard>
     <![CDATA[
-    Debug functions, like var_dump() and print_r(), should not be used in production code.
-    ]]>
-    </standard>
-    <standard>
-    <![CDATA[
-    Functions that can lead to full path disclosure, like phpinfo(), should not be used.
+    Certain development functions should not be used. This includes debug functions like var_dump() and print_r(), as well as functions that can lead to full path disclosure like phpinfo().
     ]]>
     </standard>
 </documentation>