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.

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 objectId encoding/decoding on json objects #90

Merged
merged 10 commits into from
Oct 17, 2016
Merged

fix objectId encoding/decoding on json objects #90

merged 10 commits into from
Oct 17, 2016

Conversation

llfbandit
Copy link
Contributor

Check that ObjectId convertion is applied to all objects that it should apply to #45

@vietj vietj added the to review label Aug 4, 2016
@karianna karianna added this to the 3.4.0 milestone Aug 4, 2016
@karianna
Copy link
Contributor

karianna commented Aug 4, 2016

@llfbandit Pretty happy with this one as well although anything that touches ids make me nervous. I'm wondering if further tests can be added around any edge cases here.

@llfbandit
Copy link
Contributor Author

Yup, I understand, I've added only 1 test but is actually processed 3 times especially with one default behaviour and one with MongoClientWithObjectIdTest which add the property useObjectId.
Also there are already plenty of other tests with Id (with long values, random values, etc).
I'll try to dig but I think we're OK.

@llfbandit
Copy link
Contributor Author

A further though about the use of useObjectId and its automatic behaviour is for nested objects, there's no recurrence made on objects (un-)wrap them.
I'm able to include it in my PR but I would ask for some validation before.

@johnoliver
Copy link
Contributor

Again slight conflict, but happy to merge when fixed. Thanks again for the contribution

Signed-off-by: Rémy NOËL <[email protected]>
@karianna
Copy link
Contributor

@llfbandit Couple of small conflicts left

Signed-off-by: Rémy NOËL <[email protected]>
Signed-off-by: Rémy NOËL <[email protected]> (reverted from commit 55c8860)
…objectId_encoding

# Conflicts:
#	vertx-mongo-client/src/main/asciidoc/dataobjects.adoc
#	vertx-mongo-client/src/main/java/io/vertx/ext/mongo/impl/MongoClientImpl.java
@@ -279,7 +279,7 @@ mongoClient.update("books", query, update, { res ->
----

To specify if the update should upsert or update multiple documents, use `link:../../groovydoc/io/vertx/groovy/ext/mongo/MongoClient.html#updateWithOptions(java.lang.String,%20io.vertx.core.json.JsonObject,%20io.vertx.core.json.JsonObject,%20io.vertx.ext.mongo.UpdateOptions,%20io.vertx.core.Handler)[updateWithOptions]`
and pass in an instance of `link:../dataobjects.html#UpdateOptions[UpdateOptions]`.
and pass in an instance of `link:../../null/dataobjects.html#UpdateOptions[UpdateOptions]`.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why ../null?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

groovy doc generation bug ? how does it look like with other languages ?

@karianna karianna merged commit d335927 into vert-x3:master Oct 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

4 participants