镜像站点 · 本页由第三方 GitHub 只读镜像提供,非 GitHub 官方站点,不接受任何登录或凭据输入。前往 github.com
Skip to content

DOC-7262 Hide the Possible errors list for clients with no method signature - #4468

Merged
andy-stark-redis merged 1 commit into
mainfrom
DOC-7262
Nov 4, 2026
Merged

andy-stark-redis merged 1 commit into
mainfrom
DOC-7262

Conversation

@andy-stark-redis

@andy-stark-redis andy-stark-redis commented Nov 4, 2026 •

Copy link
Copy Markdown
Contributor

Moves the api-methods-errors.html call inside the if $clientSigs branch of api-methods-tab.html, so a client with no method signature no longer shows a "Possible errors" list under "No method signature available for this client."

Checked on a full Hugo build:

  • EVALSHA: the list shows for the ten clients with signatures and not for redis_rs_sync or redis_rs_async.
  • SET: the list shows for all twelve clients.
  • index.html.md and index.json for both commands carry no Possible errors block, so nothing changed there.

The ticket names ioredis, but the API Methods dropdown has no ioredis section, so that case wasn't checked. The dropdown wasn't clicked through in a browser.

🤖 Generated with Claude Code


Note

Low Risk
Documentation template-only change with no auth, data, or runtime behavior impact.

Overview
Possible errors on command reference API Methods tabs now render only when that client has a method signature, not alongside the “No method signature available for this client.” message.

The api-methods-errors.html partial is moved from the outer client block into the if $clientSigs branch in api-methods-tab.html, so clients like redis_rs_sync / redis_rs_async on commands such as EVALSHA no longer show an errors list without a signature. Clients with signatures are unchanged.

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

…nature

The Possible errors block that DOC-7253 added to the API Methods tab rendered after the signature if/else, so a client with no signature (redis-rs for EVALSHA) showed "No method signature available for this client." followed by an error list. The partial call now sits inside the `if $clientSigs` branch. The ticket's second option, keeping the list and rewording the empty text, was dropped because the empty-signature text is shared by every command and the list is only useful beside a signature.

Checked on a full Hugo build: EVALSHA shows the list for the ten clients with signatures and none for redis_rs_sync and redis_rs_async, and SET shows it for all twelve. The page's index.html.md and index.json carry no Possible errors block, so there was nothing to change there. The ticket names ioredis as an affected client, but the dropdown has no ioredis section (Node.js maps to node_redis only), so that case could not be checked.

Learned: the Possible errors block belongs only beside a rendered signature, and the dropdown has no ioredis section
Constraint: api-methods-errors.html is called only inside the `if $clientSigs` branch of api-methods-tab.html
Gaps: the client dropdown was not clicked through in a browser, only the rendered HTML was inspected
Ticket: DOC-7262
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Nov 4, 2026 •

Copy link
Copy Markdown
Contributor

DOC-7262

@github-actions

github-actions Bot commented Nov 4, 2026 •

Copy link
Copy Markdown
Contributor

🧠 Redis Memory

Found 5 related items from repository history (5 new this commit):

Memory updated at e683535

@andy-stark-redis
andy-stark-redis requested a review from a team November 4, 2026 16:54
@andy-stark-redis andy-stark-redis self-assigned this Nov 4, 2026
@andy-stark-redis andy-stark-redis added bug Something isn't working clients Client library docs labels Nov 4, 2026

@dwdougherty dwdougherty left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

LGTM.

@andy-stark-redis

Copy link
Copy Markdown
Contributor Author

Thanks @dwdougherty !

@andy-stark-redis
andy-stark-redis merged commit fa3b007 into main Nov 4, 2026
109 checks passed
@andy-stark-redis
andy-stark-redis deleted the DOC-7262 branch November 4, 2026 17:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working clients Client library docs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants