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

feat: add sortedSetRemoveElement api #222

Merged
merged 1 commit into from
Oct 17, 2024
Merged

feat: add sortedSetRemoveElement api #222

merged 1 commit into from
Oct 17, 2024

Conversation

rishtigupta
Copy link
Contributor

PR Description:

  • add sortedSetRemoveElement api
  • add integ tests

Issue

#213

Copy link
Collaborator

@malandis malandis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I left some comments for later; let's not blocking merging this. We can address the other issues in a followup PR since CI takes a while.

src/Cache/CacheClient.php Show resolved Hide resolved
src/Cache/CacheClient.php Show resolved Hide resolved
@@ -3297,6 +3297,59 @@ public function testSortedSetFetchByRankWithNegativeStartRankLessThanEndRank_Thr
$this->assertEquals(MomentoErrorCode::INVALID_ARGUMENT_ERROR, $response->asError()->errorCode());
}

public function testSortedSetRemoveElement_HappyPath()
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TODO: also test a sorted set with multiple elements:

  • remove an element in the sorted set; the sorted set is still there but lacking that element
  • remove an element not in the sorted set; the sorted set is the same as before

@rishtigupta rishtigupta merged commit f1948f2 into main Oct 17, 2024
5 checks passed
@rishtigupta rishtigupta deleted the feat/sorted-set branch October 17, 2024 16:12
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.

2 participants