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.

Sign up for GitHub

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

Jump to bottom

Client: Why is isReady not exposed #2123

Closed
cattermo opened this issue May 9, 2022 · 0 comments
Closed

Client: Why is isReady not exposed #2123

cattermo opened this issue May 9, 2022 · 0 comments
Labels
Bug

Comments

@cattermo
Copy link

cattermo commented May 9, 2022

Could the isReady property from the socket please be exposed through the client?

I'm trying to build a failsafe implementation and since some command will just stuck if no connection (subscribe for example) I need to check if the client is ready before calling those.
@cattermo cattermo added the Bug label May 9, 2022
leibale added a commit to leibale/node-redis that referenced this issue May 9, 2022
@leibale
fix redis#2123 - expose is ready
c19d678
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cattermo