-
Notifications
You must be signed in to change notification settings - Fork 2.6k
ResponseT
shouldn't be async when using sync Redis class
#3497
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
Comments
@patrick91 Hey, thanks for reaching out! The problem is that both of clients sync and async uses the same |
@vladvildanov at this point you may as well remove You could also use generics for this which should work pretty well. |
Agreed. Incorrect types is worse than no types. |
@rafales @mvanderlee do you have time to send a PR to fix this issue? I've been meaning too but got busy with other projects 😊 But I think it should be doable and hopefully @vladvildanov will like the approach |
This code here:
Shows:
Which I think is wrong, since the return type should be
Any
instead[1], right?I think we might separate
ResponseT
for Redis and async Redis, what do you think?I haven't sent a PR for this, because it will touch quite a few files, so I wanted to double check with you all first 😊
[1] We should allow using generics for return types, but that's another issue 😊
The text was updated successfully, but these errors were encountered: