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 missing namespaced srem? method #224

Merged
merged 8 commits into from Jun 3, 2023

Conversation

neilchandler
Copy link
Contributor

@neilchandler neilchandler commented May 24, 2023

This is an extension of the exising Pull Request #223 to add the missing namespacing to the srem? method

@PatrickTulskie PatrickTulskie self-requested a review May 24, 2023 13:02
class << self
attr_accessor :sadd_returns_boolean
attr_accessor :sadd_returns_boolean, :srem_returns_boolean
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I've added the boolean here so the use of sadd_returns_boolean in flipper-redis can be updated
with new method redis_srem_returns_boolean? can be added similar to redis_sadd_returns_boolean?.
Then redis_srem_returns_boolean? could be used instead of redis_sadd_returns_boolean?
which would make more sense in this context

@PatrickTulskie
Copy link
Contributor

@neilchandler hey sorry didn't realize this conflicted with #223 before I merged it in. Can you rebase/resolve conflicts and I'll get it in?

@@ -138,7 +138,7 @@ class Namespace
"rpush" => [ :first ],
"rpushx" => [ :first ],
"sadd" => [ :first ],
"sadd?" => [ :first ],
"sadd?" => [ :first ],
Copy link
Contributor

Choose a reason for hiding this comment

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

Already addressed in #223

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This has been addressed in the rebase

@neilchandler
Copy link
Contributor Author

Hey @PatrickTulskie. I've rebased and resolved the conflicts as requested 🙂

@PatrickTulskie
Copy link
Contributor

Hey @PatrickTulskie. I've rebased and resolved the conflicts as requested slightly_smiling_face

Hey it still won't let me rebase/merge in your PR due to conflicts. Can you maybe just squash your PR into a single commit and see if that resolves it?

@PatrickTulskie PatrickTulskie merged commit 6395515 into resque:master Jun 3, 2023
71 of 72 checks passed
@PatrickTulskie
Copy link
Contributor

nvm I just did it with github. easy peasy. working on a new release this weekend.

@PatrickTulskie
Copy link
Contributor

This is in 1.11.0

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

2 participants