DOC-6353 added basic Ruby support#2874
Conversation
🛡️ Jit Security Scan Results
✅ No security findings were detected in this PR
Security scan by Jit
|
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
| "C#-Async"={quickstartSlug="dotnet", langId="csharp", clientId="stackexchange-redis", clientName="StackExchange.Redis", mappingClientId="nredisstack_async"} | ||
| "RedisVL"={quickstartSlug="redis-vl", langId="python", clientId="redis-vl", clientName="RedisVL", mappingClientId="redis_vl"} | ||
| "PHP"={quickstartSlug="php", langId="php", clientId="predis", clientName="Predis", mappingClientId="php"} | ||
| "Ruby"={quickstartSlug="redis-rb", langId="ruby", clientId="redis-rb", clientName="redis-rb", mappingClientId="redis_rb"} |
There was a problem hiding this comment.
Wrong quickstartSlug causes broken Ruby guide link
High Severity
The Ruby config entry uses quickstartSlug="redis-rb", but the actual guide page lives at content/develop/clients/ruby/, not content/develop/clients/redis-rb/. The tabbed examples template builds a link using "develop/clients/" + quickstartSlug, so this produces a link to develop/clients/redis-rb/ which is a 404. The slug needs to be "ruby" to match the directory name, consistent with how all other clients (e.g. "php" → php/, "rust" → rust/) map their slugs to their guide directories.
dwdougherty
left a comment
dwdougherty
left a comment
There was a problem hiding this comment.
Do people still use Ruby?! 🤣 Anyway, language LGTM.
|
@dwdougherty Well, the Tiobe index says it is currently at number 30 but maybe it is disproportionately used for Redis apps :-) Anyway, thanks for the review! |
2 participants
NOTE: This is just preparation for now - I'm not sure if we're ready to launch support for Ruby just yet, so don't merge.
Just the basic landing page for redis-rb and TCE support.
Note
Medium Risk
Primarily doc/content additions, but it also changes example-build mappings/config, which could affect site builds and example rendering if the new client IDs or language filters don’t match existing pipelines.
Overview
Adds initial Ruby client support by introducing a new
redis-rbclient component, surfacing it inclientsExamples, and wiring Ruby into the examples ingestion pipeline.This includes a new Ruby client landing page (
content/develop/clients/ruby/_index.md), updates the main clients index to list Ruby as a documented/supported client and cleans up the “best effort” note formatting, plus a new local Rubylandingcode example and.rb/Rubymappings to ensure Ruby examples are discovered and rendered.Written by Cursor Bugbot for commit 36e018b. This will update automatically on new commits. Configure here.