DOCSP-39852: Fluent API #118
Conversation
rustagir
left a comment
rustagir
left a comment
There was a problem hiding this comment.
Looks great, awesome work on this hefty PR - lmk if you want me to take another look after fixing small errors
| chaining option builder functions one at a time. | ||
| .. note:: Setting Options | ||
|
|
||
| Beginning in {+driver-short+} v3.0, you can set ``FineOneAndDeleteOptions`` fields by |
There was a problem hiding this comment.
S: since this change will only appear in v3 docs, no need to specify the version
| Beginning in {+driver-short+} v3.0, you can set ``FineOneAndDeleteOptions`` fields by | |
| You can set ``FindOneAndDeleteOptions`` fields by |
There was a problem hiding this comment.
I noticed this typo in other places as well, maybe Ctrl F to make sure it's spelled correctly everywhere
|
|
||
| The following table describes the options available in | ||
| ``FineOneAndDeleteOptions``: | ||
| ``FineOneAndUpdateOptions``: |
There was a problem hiding this comment.
| ``FineOneAndUpdateOptions``: | |
| ``FindOneAndUpdateOptions``: |
|
|
||
| The following table describes the options available in | ||
| ``FindOneAndReplaceOptions``: | ||
| ``FineOneAndReplaceOptions``: |
There was a problem hiding this comment.
| ``FineOneAndReplaceOptions``: | |
| ``FindOneAndReplaceOptions``: |
| creation of many different types, including ``FindOptions``. You can | ||
| use each type's ``builder()`` method to construct an options instance | ||
| by chaining option builder functions one at a time. | ||
| Beginning in {+driver-short+} v3.0, you can set ``FindOptions`` fields by chaining |
There was a problem hiding this comment.
Same comment as earlier - remove
|
|
||
| When you attempt to insert these documents, the result depends on the | ||
| value of the ``ordered`` option in your ``InsertManyOptions``: | ||
| ``ordered`` value passed to the ``ordered()`` option builder method: |
There was a problem hiding this comment.
| ``ordered`` value passed to the ``ordered()`` option builder method: | |
| value passed to the ``ordered()`` option builder method: |
| creation of many different types, including ``GridFsBucketOptions``. You | ||
| can use the ``builder()`` method to construct an instance of each type | ||
| creation of some struct types, including ``GridFsBucketOptions``. You can | ||
| use the ``builder()`` method to construct an instance of each type |
There was a problem hiding this comment.
Q: just checking that the gridFS api is still using builders to create options
|
|
||
| let filter = doc! { "year": 2015 }; | ||
| let mut cursor = collection.find(filter, opts).await?; | ||
| let mut cursor = collection |
There was a problem hiding this comment.
Q: with all these line changes, can you check that theres no code highlighting that was affected?
source/faq.txt
Outdated
|
|
||
| let my_coll: Collection<Actor> = client.database("db").collection("actors"); | ||
| let mut cursor = my_coll.find(None, None).await?; | ||
| let mut cursor = my_coll.find(None).await?; |
There was a problem hiding this comment.
| let mut cursor = my_coll.find(None).await?; | |
| let mut cursor = my_coll.find(doc! {}).await?; |
| doc! { "title": "Peter Pan" }, | ||
| None | ||
| )?; | ||
| let result = collection.find_one(doc! { "title": "Peter Pan" })?; |
There was a problem hiding this comment.
Unfortunately, for the sync API the switch to fluent methods means they now need a .run() to execute; there's no natural terminator like .await is for the async API. So this becomes:
let result = collection.find_one(doc! { "title": "Peter Pan" }).run()?;
and similar for other places below.
3 participants
Pull Request Info
PR Reviewing Guidelines
JIRA - https://jira.mongodb.org/browse/DOCSP-39852
Staging - https://preview-mongodbnorareidy.gatsbyjs.io/rust/DOCSP-39852-fluent-api/
Self-Review Checklist