Skip to content
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

fix: ZMSCORE return value if key does not exist #4697

Merged
merged 5 commits into from
Mar 5, 2025

Conversation

vyavdoshenko
Copy link
Contributor

@vyavdoshenko vyavdoshenko commented Mar 4, 2025

fix: ZMSCORE return value if key does not exist #4670

@vyavdoshenko vyavdoshenko changed the title ZMSCORE if sorted set does not exist fix fix: ZMSCORE if sorted set does not exist fix Mar 4, 2025
@adiholden
Copy link
Collaborator

Nit: I would make it explicit in the PR title that the fix is in the return value
i.e : fix: ZMSCORE return value if key does not exist

@vyavdoshenko vyavdoshenko changed the title fix: ZMSCORE if sorted set does not exist fix fix: ZMSCORE return value if key does not exist Mar 5, 2025
@vyavdoshenko vyavdoshenko force-pushed the bobik/ZMSCORE-sorted-set-does-not-exist branch from c34e039 to 1876a9a Compare March 5, 2025 09:40
@kostasrim
Copy link
Contributor

🚢 🇮🇹 👨‍🍳

@vyavdoshenko vyavdoshenko enabled auto-merge (squash) March 5, 2025 10:06
@vyavdoshenko vyavdoshenko merged commit 28e1a48 into main Mar 5, 2025
10 checks passed
@vyavdoshenko vyavdoshenko deleted the bobik/ZMSCORE-sorted-set-does-not-exist branch March 5, 2025 10:28
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.

None yet

3 participants