Add codespell suggestions for enabke and friends

[FortiShield]

PR Type

Enhancement, Tests, Bug fix

---

Description

• Improved regex patterns and formatting in codetypo/_codetypo.py.

• Enhanced test parameterization and assertions in codetypo/tests/test_dictionary.py.

• Updated and expanded typo corrections in codetypo/data/dictionary.txt.

• Upgraded dependencies in .pre-commit-config.yaml.

---

Changes walkthrough 📝

	Relevant files
Enhancement	_codetypo.py Refined regex patterns and string formatting                          codetypo/_codetypo.py Adjusted regex patterns for better matching and readability. Improved string formatting for clarity and consistency. +5/-7      dictionary.txt Expanded typo corrections and mappings                                      codetypo/data/dictionary.txt Added numerous new typo corrections and mappings. Expanded coverage for common and rare typos. Improved mappings for better accuracy. +103/-8  dictionary_rare.txt Removed rare typo mappings                                                              codetypo/data/dictionary_rare.txt Removed specific rare typo mappings for lien and liens. +0/-2      dictionary_usage.txt Removed specific usage typo mapping                                            codetypo/data/dictionary_usage.txt Removed typo mapping for blueish. +0/-1
Tests	test_dictionary.py Improved test parameterization and assertions                        codetypo/tests/test_dictionary.py Enhanced test parameterization for clarity. Improved assertion formatting for better readability. Adjusted test logic to ensure correctness. +16/-16
Dependencies	.pre-commit-config.yaml Updated pre-commit dependencies                                                    .pre-commit-config.yaml Upgraded mdformat to version 0.7.22. Upgraded ruff-pre-commit to version 0.9.10. Upgraded mypy to version 1.15.0. +3/-3

---

Need help?

Type /help how to ... in the comments thread for any questions about Qodo Merge usage.

Check out the documentation for more information.

Summary by CodeRabbit

• Chores

  • Upgraded internal tooling dependencies to benefit quality checks.

• Bug Fixes

  • Corrected numerous spelling mistakes and updated dictionary entries for improved suggestion accuracy.

• Refactor / Style

  • Streamlined code formatting and improved readability through consolidation and minor adjustments.

• Tests

  • Enhanced test clarity by refining string handling and parameter formatting without altering functionality.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates pre-commit hook versions, refactors assertion messages for readability, modifies a regular expression and f-strings in _codetypo.py, and adds codespell suggestions to the dictionaries.

Updated class diagram for inline ignore regex

classDiagram
  class inline_ignore_regex {
    -pattern: str
    +compile(pattern: str)
  }
  note for inline_ignore_regex "The regex pattern was modified to allow zero or more spaces after the colon in 'codetypo:ignore'."

Loading

File-Level Changes

Change	Details	Files
Updates dependencies in .pre-commit-config.yaml to newer versions.	Updates mdformat from 0.7.21 to 0.7.22. Updates ruff-pre-commit from v0.8.6 to v0.9.10. Updates mirrors-mypy from v1.14.1 to v1.15.0.	.pre-commit-config.yaml
Refactors assertion messages in test_dictionary.py for improved readability.	Replaces multi-line string concatenation with parenthesized expressions for better formatting in assertion messages. This change improves readability without altering the logic.	codetypo/tests/test_dictionary.py
Updates regular expression for inline ignores and modifies string formatting in _codetypo.py.	Modifies the inline_ignore_regex to allow zero or more whitespace characters after the non-word character. Updates f-strings to improve readability by adding spaces inside the curly braces.	codetypo/_codetypo.py
Adds codespell suggestions to the dictionaries.	Updates dictionary.txt with codespell suggestions. Updates dictionary_rare.txt with codespell suggestions. Updates dictionary_usage.txt with codespell suggestions.	codetypo/data/dictionary.txt codetypo/data/dictionary_rare.txt codetypo/data/dictionary_usage.txt

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Walkthrough

The pull request upgrades pre-commit hook repository versions in .pre-commit-config.yaml, modifies string formatting and regex expressions in codetypo/_codetypo.py, and applies extensive spelling corrections and removals in multiple dictionary files. Additionally, test files have been reformatted to streamline file writing and refine assertion parameterization. These changes enhance code readability and dictionary accuracy while preserving original functionality.

Changes

File(s)	Change Summary
.pre-commit-config.yaml	Updated repository versions: mdformat (0.7.21 → 0.7.22), ruff-pre-commit (v0.8.6 → v0.9.10), mypy (v1.14.1 → v1.15.0)
codetypo/_codetypo.py	Improved string formatting; modified regex (changed \s? to \s*) for inline ignore directives; refined print output formatting
codetypo/data/dictionary.txt, .../dictionary_rare.txt, .../dictionary_usage.txt	Corrected numerous spelling errors with additions and removals of dictionary entries
codetypo/tests/test_basic.py, codetypo/tests/test_dictionary.py	Consolidated file write string literals; updated test parameterization and assertion formatting

Suggested reviewers

• NxPKG
• FortiShield

Poem

I’m a rabbit hopping through the code so neat,
Nibbling bugs and tweaks with every beat.
Versions updated, spelling errors tamed,
Each change a carrot, perfectly framed.
Hopping with joy as the code sings its tune,
Celebrating clarity under the coding moon.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bbda721 and fab72bc.

📒 Files selected for processing (7)

• .pre-commit-config.yaml (3 hunks)
• codetypo/_codetypo.py (3 hunks)
• codetypo/data/dictionary.txt (39 hunks)
• codetypo/data/dictionary_rare.txt (0 hunks)
• codetypo/data/dictionary_usage.txt (0 hunks)
• codetypo/tests/test_basic.py (1 hunks)
• codetypo/tests/test_dictionary.py (5 hunks)

💤 Files with no reviewable changes (2)

• codetypo/data/dictionary_usage.txt
• codetypo/data/dictionary_rare.txt

⏰ Context from checks skipped due to timeout of 90000ms (7)

• GitHub Check: 3.12
• GitHub Check: 3.9
• GitHub Check: 3.8
• GitHub Check: 3.12
• GitHub Check: 3.11
• GitHub Check: 3.10
• GitHub Check: 3.8

🔇 Additional comments (53)

.pre-commit-config.yaml (3)

7-7: Pre-commit hook version updated

The mdformat hook version has been updated from 0.7.21 to 0.7.22, which includes the latest improvements and bug fixes.

---

61-61: Pre-commit hook version updated

The ruff-pre-commit hook version has been updated from v0.8.6 to v0.9.10, which includes newer linting rules and code formatting improvements.

---

75-75: Pre-commit hook version updated

The mypy hook version has been updated from v1.14.1 to v1.15.0, which includes the latest type checking enhancements.

codetypo/tests/test_basic.py (1)

371-371: Improved code formatting

The three separate string literals have been consolidated into a single multi-line string, which improves readability while maintaining identical functionality.

codetypo/_codetypo.py (4)

61-62: Improved code readability

The multi-line string for uri_regex_def has been condensed into a single line, which improves code readability while maintaining the same regex pattern and functionality.

---

63-63: Enhanced regex pattern

The inline_ignore_regex pattern has been modified to use \s* (zero or more whitespace characters) instead of \s? (zero or one whitespace character). This broadens the matching capability for the codetypo:ignore directive, allowing for any amount of whitespace between the non-word character and the directive.

---

765-767: Improved string formatting

The spacing in the string formatting for line_ui has been adjusted to include spaces after the colon in the slicing operation, improving readability without changing the logic.

---

1059-1059: Consistent string formatting

The print statement has been modified to remove an extra space before the ==> symbol, streamlining the output format and ensuring consistency.

codetypo/tests/test_dictionary.py (6)

50-51: Improved parameter declaration

The parameter definition in pytest.mark.parametrize has been changed from a string format to a tuple format. This change improves type checking and IDE support while maintaining the same functionality.

---

147-149: Enhanced assertion formatting

The assertion statement has been reformatted to separate the condition from the error message, placing the error message in parentheses. This improves readability and maintainability without altering the test behavior.

---

169-171: Enhanced assertion formatting

The assertion statement has been reformatted to separate the condition from the error message, placing the error message in parentheses. This improves readability and maintainability without altering the test behavior.

---

188-190: Enhanced assertion formatting

The assertion statement has been reformatted to separate the condition from the error message, placing the error message in parentheses. This improves readability and maintainability without altering the test behavior.

---

310-312: Enhanced assertion formatting

The assertion statement has been reformatted to separate the condition from the error message, placing the error message in parentheses. This improves readability and maintainability without altering the test behavior.

---

319-321: Enhanced assertion formatting

The assertion statement has been reformatted to separate the condition from the error message, placing the error message in parentheses. This improves readability and maintainability without altering the test behavior.

codetypo/data/dictionary.txt (39)

834-841: Accurate corrections for accelerometer-related typos
The corrections for entries such as “accleometer” to “accelerometer” and “accleometers” to “accelerometers” (along with the other related fixes) are clear and consistent.

---

3395-3401: Consistent alignment typo corrections
All variants related to “alignment” (e.g. “aligments,” “aligmnet,” “aligmnets,” etc.) have been corrected uniformly.

---

4464-4470: Typo fixes for compound words and ambiguous mapping
Corrections for “andthe,” “andtoid,” and “andtoids” are straightforward. Note that the mapping for “ane” to “and, one,” introduces multiple suggestions—please verify that this is the intended behavior.

---

7170-7176: Refined corrections for ‘assessin’ variants
The changes addressing “assessin,” “assessmant,” “assessmants,” and “assests” (as well as the asphalt-related typos) appear comprehensive and are formatted to suggest multiple correct forms where needed.

---

10437-10446: Accurate fixes for Bugzilla and related typos
The corrections, including “buzilla” to “bugzilla,” “bve” to “be,” and the replacement of hyphenated “by-pass” variants with their unhyphenated forms, are correctly applied.

---

10826-10837: Reliable corrections for caller and cancellation typos
Adjustments for “calloed,” “callser,” and the various mis‑spelled “cancel” forms (e.g. “calncel,” “calncellation,” etc.) are accurate and improve consistency.

---

13438-13445: Uniform updates for coefficient spellings
The multiple fixes addressing “coeffiecients,” “coeffient,” “coeffitient,” and similar entries now consistently map to the correct form “coefficient(s).”

---

16179-16185: Correcting variations of “consist” and related words
The updates correcting “constext,” “consting,” “constinually,” and “constist” (with its multiple acceptable forms) are well executed.

---

16381-16387: Improved container-related typo fixes
Corrections for “containter,” “containters,” and “containting” are properly handled. The mapping for “containts” now offers “contains, constraints,” which should be verified for intended usage.

---

17546-17556: Consistent corrections for correspondence-related typos
The changes replacing “corretor,” “corretors,” and especially the series starting with “correxpond” (leading to “correspond,” “correspondence,” etc.) are precise and improve clarity.

---

17810-17817: Proper fixes for counselling and constructor typos
The corrections for “counsellin,” “counsil,” and the mapping of “counstructor” to “constructor” (including its plural form) look correct.

---

17866-17879: Comprehensive corrections for count/countdown typos
The adjustments for multiple variations—from “coutn” to “count” and related forms like “coutndown” to “countdown”—are applied consistently.

---

18121-18127: Effective updates for criteria-related typos
Correcting “critcials,” “critera,” and “criteras” ensures that all forms of the word now consistently map to “criteria” (or “criterion” where appropriate).

---

18158-18164: Accurate fixes for critique and crocodile typos
The corrections for “critque,” “critqued,” and “critquing” along with the subsequent mapping for “critreria” to “criteria” are well done. The changes for “croch,” “crockadile,” and “crockodiles” further enhance accuracy.

---

18737-18745: Precise correction of draw-related typos
Updates such as “darw” to “draw,” “darwn” to “drawn, Darwin,” and “darws” to “draws” as well as fixes for “dasboard” ensure proper spelling throughout.

---

21328-21337: Reliable corrections for discarded and dictated variations
The series of adjustments for entries like “dicarded,” “dicarding,” “dicards,” and subsequently “dicate,” “dicated,” “dicates,” etc., now accurately yield their intended forms.

---

21378-21387: Robust updates for discrimination and dictation typos
The comprehensive fixes—from “dicslosure” to “disclosure” and “dictacte” to “dictate” along with their related forms—are consistently applied.

---

21690-21696: Consistent dimension-related typo corrections
The modifications that correct “dimensionailties,” “dimensionailty,” and “dimensionned” (among others) now enforce consistent use of “dimension,” “dimensionality,” or “dimensionalities” as appropriate.

---

22551-22559: Clear fixes for distance-related typos
Corrections for “distace,” “distaced,” “distaces,” and the subsequent series (“distacne,” “distacned,” “distacnes,” etc.) ensure that the word “distance” is used consistently.

---

22804-22813: Accurate updates for division and delay typos
The changes for “divsions,” “divsiors,” and even “djanog” (to “Django”) alongside corrections for “dleay” variants are well implemented.

---

24263-24272: Uniform fixes for enablement typos
Entries such as “enabels,” “enabes,” “enabing,” and the corrected variants (“enabke,” “enabked,” etc.) now consistently produce “enables,” “enabled,” or “enabling” as required.

---

31931-31942: Thorough corrections for implementation improvements
Adjustments that correct “impplementating,” “impplementation,” “impplemented,” and subsequent “impprove” series are comprehensive and enforce uniform spelling.

---

32886-32892: Effective corrections for informational typos
Mapping fixes for “informtional,” “inforrmation,” and “inforrmational” (with “infp” corrected to “info”) are accurate; infrastructure-related corrections further bolster consistency.

---

36416-36422: Accurate fixes for light-related typos
The corrections addressing “ligher,” “lighers,” “lighing,” and the updated “lighning” alongside “lightbulp” and “lightin” are applied correctly.

---

41558-41568: Consistent open/operate typo corrections
Updates to terms like “opeming,” “opems,” “openbrower” and the refined changes (e.g. “opend” to “opened,” “openend” to “opened”) ensure clarity and uniformity.

---

42237-42246: Well-executed fixes for oscillation and association typos
The transformation of “osffsets” to “offsets,” “osicllations” to “oscillations,” and the series converting “ossociate” variants are correctly handled.

---

45155-45161: Clear corrections for practice-related typos
The adjustments correcting “practicval,” “practioner(s),” and “practive” (with additional mapping to “proactive” where relevant) are consistent and correct.

---

45218-45227: Accurate handling of pre- formatted typos
Corrections adjusting “pre-procesing,” “pre-realease,” “pre-registeres” to their proper forms—and the normalization of “pre-select” variants—are implemented uniformly.

---

45596-45605: Reliable updates for preselect and presentation typos
The corrections from “presearving” to “preserving” and the subsequent fixes for “preselet” variants (as well as presentation-related typos) are accurately applied.

---

45902-45908: Consistent fixes for prioritization typos
The series of corrections (e.g. “priorizes,” “priorizin,” “priorizing” and the mapping of “priort” to “prior” with alternatives) are clear and maintain consistency.

---

51293-51299: Simple and correct fixes for return-related typos
The changes correcting “returnn,” “returnned,” “returnning,” and “returnst” effectively normalize these entries to “return” or “returns.”

---

54488-54494: Accurate correction of synthetics and social typos
The updates, including “snythetics” to “synthetics” and the consistent correction of “socail/socal” to “social” (and related forms), are cleanly applied.

---

54953-54960: Precise fixes for specificity-related typos
Corrections addressing “specically,” “specication,” “specications” and the subsequent normalization of “specicification” and “specicifications” are well executed.

---

56497-56504: Uniform corrections for subscription typos
The changes replacing “subscibed,” “subsciber,” “subscibers” with their proper forms—and the normalization of “subsciption” related variants—are correct.

---

59079-59085: Consistent timeout-related typo corrections
Updates that correct “timemouts,” “timeot,” “timeots,” and the refined changes for “timeour” and others are applied accurately.

---

60316-60329: Comprehensive fixes for attempting and test-related typos
The multiple corrections for “tryinng,” “trys,” “tryying,” and particularly the series for “ttempt,” “ttest,” etc. are thorough and ensure consistency across the dictionary.

---

61286-61295: Effective corrections for unmapped and unmistakable typos
The fixes transforming “unmappend,” “unmarsalling,” “unmaximice” and the subsequent corrections for “unmber” variants are clear and appropriately standardize the entries.

---

62105-62111: Clean update of utilize-related typos
The corrections addressing “utilitize,” “utilitizes,” “utilitizing” and especially the change from “utiliy” to “utility” enforce uniformity across these entries.

---

63320-63327: Final corrections for warranty and warehouse typos
The adjustments for “waranties,” “waranty,” “wardobe,” and the series updating “warehosue” variants are accurate and complete.

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[codiumai-pr-agent-free]

CI Feedback 🧐

(Feedback updated until commit fab72bc)

A test triggered by this PR failed. Here is an AI-generated analysis of the failure:

Action: package

Failed stage: Install dependencies [❌]

Failure summary: The action failed because of a package hash mismatch during the Python package installation process. The hash of a downloaded package does not match the expected hash specified in the requirements file. This is a security feature that prevents the installation of potentially tampered packages. Specifically: Expected SHA256: 9ea1544ad55cecf4b8242fab6dd35a93bbce657034b0611ee383099054ab6d8c Actual SHA256: c86c5b37532d35aa6425316d7383caebb23320aaf651ef416f122cd4cf2d148b The package name was not specified in the error message (shown as "unknown package")

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 233: Downloading cryptography-44.0.2-cp39-abi3-manylinux_2_34_x86_64.whl (4.2 MB) 234: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 4.2/4.2 MB 109.0 MB/s eta 0:00:00 235: Downloading mdurl-0.1.2-py3-none-any.whl (10.0 kB) 236: Downloading zipp-3.21.0-py3-none-any.whl (9.6 kB) 237: Downloading backports.tarfile-1.2.0-py3-none-any.whl (30 kB) 238: Downloading more_itertools-10.6.0-py3-none-any.whl (63 kB) 239: Downloading cffi-1.17.1-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (446 kB) 240: Downloading pycparser-2.22-py3-none-any.whl (117 kB) 241: ERROR: THESE PACKAGES DO NOT MATCH THE HASHES FROM THE REQUIREMENTS FILE. If you have updated the package versions, please update the hashes. Otherwise, examine the package contents carefully; someone may have tampered with them. 242: unknown package: 243: Expected sha256 9ea1544ad55cecf4b8242fab6dd35a93bbce657034b0611ee383099054ab6d8c 244: Got c86c5b37532d35aa6425316d7383caebb23320aaf651ef416f122cd4cf2d148b 245: ##[error]Process completed with exit code 1.

[codiumai-pr-agent-free]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 PR contains tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Typo Mapping Consistency The PR adds new typo mappings but some may need verification for consistency with existing patterns. For example, "ane->and, one," vs previous "ane->and" and "constist->consist, consists," vs previous "constist->consist". ane->and, one, Regex Pattern Change The inline_ignore_regex pattern was modified from "r"[^\\w\\s]\s?codetypo:ignore\b" to "r"[^\\w\\s]\s*codetypo:ignore\b". This changes the whitespace matching behavior from optional single space to any amount of whitespace. inline_ignore_regex = re.compile(r"[^\w\s]\s*codetypo:ignore\b(\s+(?P<words>[\w,]*))?")

[codiumai-pr-agent-free]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Preserve original regex behavior The regex pattern change from \s? to \s could potentially match different text patterns than before. The original pattern required at most one whitespace character, while the new pattern allows any number of whitespace characters. This might cause unexpected behavior if there are multiple spaces before "codetypo:ignore".* codetypo/_codetypo.py [63] -inline_ignore_regex = re.compile(r"[^\w\s]\s*codetypo:ignore\b(\s+(?P<words>[\w,]*))?") +inline_ignore_regex = re.compile(r"[^\w\s]\s?codetypo:ignore\b(\s+(?P<words>[\w,]*))?") Apply this suggestion Suggestion importance[1-10]: 7 __ Why: The suggestion correctly identifies a potential behavior change in the regex pattern. Changing from \s? (0 or 1 whitespace) to \s* (0 or more whitespaces) could alter how the code identifies ignore directives, potentially causing the tool to recognize patterns it previously wouldn't. This could impact functionality.	Medium
More

[sourcery-ai]

Hey @FortiShield - I've reviewed your changes - here's some feedback:

Overall Comments:

• Consider grouping the dictionary changes into a separate commit from the code changes.
• It's great that you're updating the pre-commit hooks to the latest versions.

Here's what I looked at during the review

• 🟡 General issues: 1 issue found
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

issue: Removing "lien" and "liens" seems incorrect.

"lien" is a valid word, although rare. It should probably stay in dictionary_rare.txt.