zrevrangebyscore(key: string, min: number | string, max: number | string, cb?: Callback<string[]>): R;
zrevrangebyscore(key: string, min: number | string, max: number | string, withscores: string, cb?: Callback<string[]>): R;
zrevrangebyscore(key: string, min: number | string, max: number | string, limit: string, offset: number, count: number, cb?: Callback<string[]>): R;
zrevrangebyscore(key: string, min: number | string, max: number | string, withscores: string, limit: string, offset: number, count: number, cb?: Callback<string[]>): R;
ZREVRANGEBYSCORE(key: string, min: number | string, max: number | string, cb?: Callback<string[]>): R;
ZREVRANGEBYSCORE(key: string, min: number | string, max: number | string, withscores: string, cb?: Callback<string[]>): R;
ZREVRANGEBYSCORE(key: string, min: number | string, max: number | string, limit: string, offset: number, count: number, cb?: Callback<string[]>): R;
ZREVRANGEBYSCORE(key: string, min: number | string, max: number | string, withscores: string, limit: string, offset: number, count: number, cb?: Callback<string[]>): R;
min and max is reversed in the argument order In redis natvie cli for ZREVRANGEBYSCORE the order should be [key max min WITHSCORES LIMIT OFFSET COUNT] probably the argument naming in the function is reversed so if I follow the native command order to input the function will work as expected.
Comment From: enjoy-binbin
You can check doc: https://redis.io/commands/zrevrangebyscore for more info. The design is like this.
At the same time, I also found some problems with the code comments... Like: https://github.com/redis/redis/blob/unstable/src/t_zset.c#L3250 https://github.com/redis/redis/blob/unstable/src/t_zset.c#L3535 https://github.com/redis/redis/blob/unstable/src/t_zset.c#L3117
diff can check: https://github.com/redis/redis/compare/unstable...enjoy-binbin:fix_comment?expand=1