From 2983d25ef861fd3c1e5c8aa526d18e2a42e2297d Mon Sep 17 00:00:00 2001
From: Dennis Snell <dennis.snell@automattic.com>
Date: Fri, 28 Jul 2023 13:49:31 -0700
Subject: [PATCH] Ignore HTML Processor until PHPCS bug is resolved.

See https://github.com/squizlabs/PHP_CodeSniffer/issues/3685

PHP Code Sniffer mistakes the following code, thinking that it
throws an exception even though the exception is caught in place.

```php
try {
	throw new WP_HTML_Unsupported_Exception( 'The outside never sees me.' );
} catch ( WP_HTML_Unsupported_Excepted $e ) {
	return false;
}
```

This patch adds an exclude for the HTML Processor where PHPCS is confused.
Until that bug is fixed this is a pragmatic solution to avoiding the need
to change actual code around a bug in a linting tool. When that bug is
fixed and it no longer gets confused this exclusion should be removed.
---
 phpcs.xml.dist | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/phpcs.xml.dist b/phpcs.xml.dist
index 43bc593090c4aa..deefb843dd4e66 100644
--- a/phpcs.xml.dist
+++ b/phpcs.xml.dist
@@ -85,6 +85,8 @@
 		<exclude-pattern>phpunit/*</exclude-pattern>
 	</rule>
 	<rule ref="Squiz.Commenting.FunctionCommentThrowTag.Missing">
+		<!-- Ignore until squizlabs/PHP_CodeSniffer#3685 is fixed: it thinks that a caught exception escapes the function. -->
+		<exclude-pattern>lib/compat/wordpress-6.4/html-api/class-wp-html-processor.php</exclude-pattern>
 		<exclude-pattern>phpunit/*</exclude-pattern>
 	</rule>