-
Notifications
You must be signed in to change notification settings - Fork 169
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 #1180: Add missing docs for ConnectOptions #1181
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for your PR!
Some review notes.
async-nats/src/options.rs
Outdated
/// By default, client construction will fail if | ||
/// the connection to the server cannot be established. | ||
/// | ||
/// Setting `retry_on_initial_connect` causes client construction |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not exactly how it works. In this case, the handle to the Client
is returned immediately and conection is handled asynchronously in the background. Otherwise users would not know the reason for initial connection failure.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure I understand - if you don't mind, have a look again.
ConnectOptions::retry_on_initial_connect and ConnectOptions::ignore_discovered_servers
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Thank you for your contribution!
Docs for
ConnectOptions::retry_on_initial_connect
andConnectOptions::ignore_discovered_servers
.