-
Notifications
You must be signed in to change notification settings - Fork 20
DOCSP-35346: Change parse method #104
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
Conversation
jordan-smith721
left a comment
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.
Just a couple clarifying questions
| // Replace the placeholder with your Atlas connection string | ||
| let uri = "<connection string>"; | ||
| let mut client_options = ClientOptions::parse(uri)?; | ||
| let mut client_options = ClientOptions::parse_async(uri)?; |
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.
Question: I noticed this is in the connection-sync file and doesn't have .await?, should this stay as just parse?
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.
Thanks for catching - yes I meant to leave as is for all the sync files! So this can stay as parse()
| let uri = "<connection string>"; | ||
| // start-stable-api-behavior | ||
| let mut client_options = ClientOptions::parse(uri)?; | ||
| let mut client_options = ClientOptions::parse_async(uri)?; |
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.
Similar question to above, since there is no await here, should it stay parse instead? Or maybe add the await call?
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.
This is also a sync file so you're right, this can stay parse()
| fn main() -> mongodb::error::Result<()> { | ||
| let uri = "<connection string>"; | ||
| let mut client_options = ClientOptions::parse(uri)?; | ||
| let mut client_options = ClientOptions::parse_async(uri)?; |
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.
Same question as above, since there is no await here, should it stay parse instead? Or maybe add the await call?
jordan-smith721
left a comment
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!
(cherry picked from commit 9cc0cca)
(cherry picked from commit 9cc0cca)
Pull Request Info
PR Reviewing Guidelines
JIRA - https://jira.mongodb.org/browse/DOCSP-35346
Staging - https://preview-mongodbnorareidy.gatsbyjs.io/rust/DOCSP-35346-parse-method/
Self-Review Checklist