Repository navigation
zrange min->start max ->stop - #1736
Conversation
zuiderkwast
left a comment
There was a problem hiding this comment.
Good idea.
Is it explained somewhere that REV needs start=max and stop=min? Maybe add that somewhere...
It would be good to add an example with REV as well.
Co-authored-by: Viktor Söderqvist <viktor@zuiderkwast.se>
|
@zuiderkwast - added another piece about the |
zuiderkwast
left a comment
There was a problem hiding this comment.
The added section about reverse ranges explains it very well.
Question: Does BYLEX REV also reverse the start and stop lexicographic order?
|
@zuiderkwast - added the bit on |
Sorry, it's in the readme: https://github.com/redis/redis-doc#styling-guidelines No need to add a blank line which will cause a new paragraph. A single linebreak in the markdown is enough and it doesn't cause any linebreak in the rendered HTML. The purpose is just to make the diff smaller when some part of the text is changed, i.e. easier to review changes. |
|
The build error is the spellcheck which doesn't like the word BYLEX. If the code example is surrounded by backticks I think it can escape the spell check. Otherwise, we need it to the |
|
Gotcha - I guess that command snippet should not have been bolded, I guess aspell automatically knows not to boot out command names? Regardless, I pushed the updates requested. |
In redis#1736 there were introduced new names of parameters 'min', 'max' (now 'start', 'stop'), but command in header wasn't updated
Accompanying PR to redis/redis#10097 to change
min->startandmax->stopinZRANGEsee other PR for explanation for change.