Open
Conversation
- Remove deprecated zlexcount(K key, String min, String max) - Remove deprecated zrangebylex(K key, String min, String max) - Remove deprecated zrangebylex(K key, String min, String max, long offset, long count) - Remove deprecated zremrangebylex(K key, String min, String max) All 4 methods have Range-based replacements already available.
- Template changes automatically propagated to generated interfaces - Removed deprecated lex methods from async/reactive variants - Auto-formatted template per project formatting rules
- Remove deprecated zlexcount(key, String, String) test calls - Remove deprecated zrangebylex(key, String, String, offset, count) test calls - Remove deprecated zremrangebylex(key, String, String) test calls - All tests now use Range-based APIs exclusively - Auto-formatted per project formatting rules Tests continue to verify same functionality with type-safe Range APIs.
|
Hi, I’m Jit, a friendly security platform designed to help developers build secure applications from day zero with an MVS (Minimal viable security) mindset. In case there are security findings, they will be communicated to you as a comment inside the PR. Hope you’ll enjoy using Jit. Questions? Comments? Want to learn more? Get in touch with us. |
17 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR follows up on the existing Sorted Set API cleanup discussions in #363 and the follow-up in #3328.
It removes deprecated lex-based ZSET overloads that accept
String min/maxparameters and consolidates lexicographical range operations around theRange/LimitAPI.Changes
RedisSortedSetCommands:zlexcount(K, String, String)zrangebylex(K, String, String)zrangebylex(K, String, String, long, long)zremrangebylex(K, String, String)Range/Limit-based lex operations while preserving boundary semanticsMotivation
These deprecated overloads duplicate existing
Range/Limit-based APIs and increase the surface area of the public API. Removing them improves consistency, reduces maintenance overhead, and aligns with the ongoing Sorted Set API cleanup planned for the next major release.Refs: #363, #3328