From 515d28d24b7b2c2acac88c398d418a6354c408db Mon Sep 17 00:00:00 2001
From: Miro <200482516+Mirochill@users.noreply.github.com>
Date: Mon, 18 May 2026 22:04:09 +0200
Subject: [PATCH] Document config handling for plugin option actions

---
 docs/source/plugin-development/plugin-parameters.rst | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/docs/source/plugin-development/plugin-parameters.rst b/docs/source/plugin-development/plugin-parameters.rst
index 931c186..478783c 100644
--- a/docs/source/plugin-development/plugin-parameters.rst
+++ b/docs/source/plugin-development/plugin-parameters.rst
@@ -109,6 +109,13 @@ Each of these options works individually or can be combined. Let's look at a
 couple examples from |Flake8|. In each example, we will have
 ``option_manager`` which is an instance of |OptionManager|.
 
+.. note::
+
+    Values read from configuration files do not go through :mod:`argparse`
+    ``action`` handlers. If an option needs the same custom transformation for
+    both command-line and configuration values, prefer ``type=`` for that
+    transformation, or use the |Flake8|-specific normalizers documented above.
+
 .. code-block:: python
 
     option_manager.add_option(