From e1d76b60cc05e5cb533c224b5055043bb5953e5b Mon Sep 17 00:00:00 2001 From: David Cain Date: Wed, 19 Jul 2023 11:25:36 -0600 Subject: [PATCH] Add missing backtick to B034 documentation (#5889) This is a great rule, but the documentation page shows some wonky formatting due to a missing backtick. Fix a typo too. Should fix display on https://beta.ruff.rs/docs/rules/re-sub-positional-args/ image --- .../src/rules/flake8_bugbear/rules/re_sub_positional_args.rs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/crates/ruff/src/rules/flake8_bugbear/rules/re_sub_positional_args.rs b/crates/ruff/src/rules/flake8_bugbear/rules/re_sub_positional_args.rs index 5e9cdddb4c..c70791d136 100644 --- a/crates/ruff/src/rules/flake8_bugbear/rules/re_sub_positional_args.rs +++ b/crates/ruff/src/rules/flake8_bugbear/rules/re_sub_positional_args.rs @@ -13,8 +13,8 @@ use crate::checkers::ast::Checker; /// /// ## Why is this bad? /// Passing `count`, `maxsplit`, or `flags` as positional arguments to -/// `re.sub`, re.subn`, or `re.split` can lead to confusion, as most methods in -/// the `re` module accepts `flags` as the third positional argument, while +/// `re.sub`, `re.subn`, or `re.split` can lead to confusion, as most methods in +/// the `re` module accept `flags` as the third positional argument, while /// `re.sub`, `re.subn`, and `re.split` have different signatures. /// /// Instead, pass `count`, `maxsplit`, and `flags` as keyword arguments.