Skip to content

Conversation

@gisu1102
Copy link

@gisu1102 gisu1102 commented Jan 5, 2026

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/max parameters and consolidates lexicographical range operations around the Range/Limit API.

Changes

  • Remove deprecated lex-based Sorted Set overloads from RedisSortedSetCommands:
    • zlexcount(K, String, String)
    • zrangebylex(K, String, String)
    • zrangebylex(K, String, String, long, long)
    • zremrangebylex(K, String, String)
  • Regenerate async and reactive Sorted Set APIs from templates
  • Update integration tests to use Range/Limit-based lex operations while preserving boundary semantics

Motivation

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

- 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.
@jit-ci
Copy link

jit-ci bot commented Jan 5, 2026

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant