Skip to content

docs: fix scan iterator example pattern - #3245

Merged
nkaradzhov merged 1 commit into
redis:masterfrom
Rohan5commit:docs/scan-iterator-pattern-20260422
Apr 22, 2026
Merged

nkaradzhov merged 1 commit into
redis:masterfrom
Rohan5commit:docs/scan-iterator-pattern-20260422

Conversation

@Rohan5commit

@Rohan5commit Rohan5commit commented Apr 22, 2026 •

Copy link
Copy Markdown
Contributor

Description

Fix the scan iterator example to use pattern* instead of patter* in the README.


Checklist

  • Does npm test pass with this change (including linting)?
  • Is the new or changed code fully tested?
  • Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?

Validation

  • Ran git diff --check

Note

Low Risk
Documentation-only change correcting a typo in the scanIterator example; no runtime behavior is affected.

Overview
Fixes a typo in the README scanIterator options example by correcting the MATCH glob from patter* to pattern*, so the docs show a valid key pattern.

Reviewed by Cursor Bugbot for commit b300d54. Bugbot is set up for automated code reviews on this repo. Configure here.

Copilot AI review requested due to automatic review settings April 22, 2026 04:05

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the README scan iterator example to use the correct MATCH glob pattern, ensuring the documented usage matches intended Redis SCAN semantics.

Changes:

  • Fix typo in the client.scanIterator example: MATCH: "patter*" → MATCH: "pattern*".

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@nkaradzhov
nkaradzhov merged commit 788bc72 into redis:master Apr 22, 2026
7 of 8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants