From fdd914adac3ef78255ded47362b2d7bbf1eafd4b Mon Sep 17 00:00:00 2001 From: Jacob Walls Date: Sat, 29 Jul 2023 19:40:15 -0400 Subject: [PATCH] Adjust news/docs from #8813 to use bad-names-rgx --- doc/data/messages/i/invalid-name/details.rst | 2 +- doc/whatsnew/fragments/2018.user_action | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/data/messages/i/invalid-name/details.rst b/doc/data/messages/i/invalid-name/details.rst index 14cfe6e592..3323bddf44 100644 --- a/doc/data/messages/i/invalid-name/details.rst +++ b/doc/data/messages/i/invalid-name/details.rst @@ -99,7 +99,7 @@ Before pylint 3.0, most predefined patterns also enforced a minimum length of three characters. If this behavior is desired in versions 3.0 and following, it can be had by providing custom regular expressions as described next. (Or, if the ``disallowed-name`` check is sufficient instead of ``invalid-name``, -providing the single option ``bad-names-rgxs="^..?$"`` will suffice to fail 1-2 +providing the single option ``bad-names-rgx="^..?$"`` will suffice to fail 1-2 character names. Custom regular expressions diff --git a/doc/whatsnew/fragments/2018.user_action b/doc/whatsnew/fragments/2018.user_action index 5e33c8388c..420fe5bccf 100644 --- a/doc/whatsnew/fragments/2018.user_action +++ b/doc/whatsnew/fragments/2018.user_action @@ -5,7 +5,7 @@ and name length, and users regularly reported this to be surprising.) If checking for a minimum length is still desired, it can be regained in two ways: - If you are content with a ``disallowed-name`` message (instead of ``invalid-name``), -then simply add the option ``bad-names-rgxs="^..?$"``, which will fail 1-2 +then simply add the option ``bad-names-rgx="^..?$"``, which will fail 1-2 character-long names. (Ensure you enable ``disallowed-name``.) - If you would prefer an ``invalid-name`` message to be emitted, or would prefer