-
Notifications
You must be signed in to change notification settings - Fork 1.7k
ZREVRANK: documentation is confusing. #2354
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi, this is expected. btw, Redis 7.2 RC1 will be release in the next week. i think the history part has nothing to do with the stable version, |
I think removing the WITHSCORE will definitely cause less confusion. But adding the current stable version to an FYI in history section would make way more sense in my opinion |
get it. sadly, i think currently we won't remove the WITHSCORE. @itamarhaber can you give some advices? |
The root cause for the "problem" is the premature merge of #2227, which should have been done sometime after next week :) That said, we've always had this issue with new commands/arguments that haven't been released yet and are introduced prematurely to the docs. Going forward, I do want to have the interactive examples run against the nightly build to avoid this from happening. |
Hey I would love to do the incorporation of this latest build into the docs. Would love to take this up. Let me know how I could contribute here |
@oranagra do you agree with ^:
|
i'm not certain i follow. p.s. i don't think you can afford to run the interactive examples against the released version, it'll mean we can't merge docs PRs of new commands that are not released yet. |
@oranagra Can you or someone suggest how the response for ZREVRANK WITHSCORE or ZRANK WITHSCORE must look like? |
Hello @SoulPancake Here you go:
Mind you, you can run Redis 7.2-rc1 and check it out locally :) |
WITHSCORE is documented in ZREVRANK saying it is available from 7.2.0 but the latest stable version is 7.0.9. Also the examples are showing an error for WITHSCORE argument, most probably for the same reason.
This is a little bit confusing. Adding the latest stable version to history could solve this.
Would love to take this up. Let me know how to contribute as I'm not able to find history section in the codebase
The text was updated successfully, but these errors were encountered: