From e7ab4f741c0ec22cf70457c7a542b7978202b10a Mon Sep 17 00:00:00 2001
From: Ondrej Mirtes <ondrej@mirtes.cz>
Date: Wed, 8 Nov 2023 14:09:04 +0100
Subject: [PATCH] Rich PHPDoc for ExceptionTypeResolver

---
 .../Exceptions/ExceptionTypeResolver.php      | 28 ++++++++++++++++++-
 1 file changed, 27 insertions(+), 1 deletion(-)

diff --git a/src/Rules/Exceptions/ExceptionTypeResolver.php b/src/Rules/Exceptions/ExceptionTypeResolver.php
index 83af9366d3..5b7ac7e965 100644
--- a/src/Rules/Exceptions/ExceptionTypeResolver.php
+++ b/src/Rules/Exceptions/ExceptionTypeResolver.php
@@ -4,7 +4,33 @@
 
 use PHPStan\Analyser\Scope;
 
-/** @api */
+/**
+ * @api
+ *
+ * This interface allows you to write custom logic that can dynamically decide
+ * whether an exception is checked or unchecked type.
+ *
+ * Because the interface accepts a Scope, you can ask about the place in the code where
+ * it's being decided - a file, a namespace or a class name.
+ *
+ * There can only be a single ExceptionTypeResolver per project, and you can register it
+ * in your configuration file like this:
+ *
+ * ```
+ *  services:
+ *      exceptionTypeResolver!:
+ *          class: PHPStan\Rules\Exceptions\ExceptionTypeResolver
+ *  ```
+ *
+ * You can also take advantage of the `PHPStan\Rules\Exceptions\DefaultExceptionTypeResolver`
+ * by injecting it into the constructor of your ExceptionTypeResolver
+ * and delegate the logic of the classes and places you don't care about.
+ *
+ * DefaultExceptionTypeResolver decides the type of the exception based on configuration
+ * parameters like `exceptions.uncheckedExceptionClasses` etc.
+ *
+ * Learn more: https://phpstan.org/blog/bring-your-exceptions-under-control
+ */
 interface ExceptionTypeResolver
 {