-
Notifications
You must be signed in to change notification settings - Fork 43
DOCSP-42961: Removed Nested Components #581
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
Changes from all commits
577890a
a54e603
8fb5894
6b40e89
07a82f5
7103e2f
19bdf64
38db069
4f85b13
75f8585
4262df6
697f184
3ebef66
646b22e
9a899e7
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
@@ -285,11 +285,7 @@ package: | |||||||||||||
|
||||||||||||||
* - ``BsonRepresentation`` | ||||||||||||||
- Specifies the BSON type used to store the value when different from the | ||||||||||||||
POJO property. | ||||||||||||||
|
||||||||||||||
.. seealso:: | ||||||||||||||
|
||||||||||||||
:ref:`bsonrepresentation-annotation-code-example` | ||||||||||||||
POJO property. See an example of :ref:`bsonrepresentation-annotation-code-example` on this page. | ||||||||||||||
|
||||||||||||||
* - ``BsonId`` | ||||||||||||||
- Marks a property to serialize as the _id property. | ||||||||||||||
|
@@ -299,28 +295,24 @@ package: | |||||||||||||
and/or deserialize a property. | ||||||||||||||
|
||||||||||||||
* - ``BsonProperty`` | ||||||||||||||
- Specifies a custom document field name when converting the POJO | ||||||||||||||
field to BSON. You can include a discriminator to serialize POJOs | ||||||||||||||
nested within the field. | ||||||||||||||
|
||||||||||||||
.. important:: | ||||||||||||||
- | Specifies a custom document field name when converting the POJO | ||||||||||||||
field to BSON. You can include a discriminator to serialize POJOs | ||||||||||||||
nested within the field. | ||||||||||||||
| | ||||||||||||||
| When applying ``@BsonProperty`` to a private field, | ||||||||||||||
**you must also add getter and setter methods for that field to serialize and | ||||||||||||||
customize the field name**. | ||||||||||||||
Comment on lines
+302
to
+304
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
S: The bolding looks a little too bold for this small section. The Style Guide suggested using the gold Important directive to replace the Important note directive: https://www.mongodb.com/docs/meta/style-guide/nested-components/#important-or-warning. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. These are being removed as part of this nested component work where we want annotations taken out of tables. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is using the gold Important directive rather than the bolding not necessary here? Meant this gold directive that the style guide recommends: https://www.mongodb.com/docs/meta/style-guide/nested-components/#important-or-warning:~:text=IMPORTANT%3A%20Data%20transfer%20as%20part%20of%20the%20backup%20and%20restore%20process%20is%20charged%20separately. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ok, LGTM! |
||||||||||||||
|
||||||||||||||
When applying ``@BsonProperty`` to a private field, you must also add | ||||||||||||||
getter and setter methods for that field to serialize and customize | ||||||||||||||
the field name. | ||||||||||||||
|
||||||||||||||
* - ``BsonExtraElements`` | ||||||||||||||
- Specifies the POJO field on which to deserialize all elements that are | ||||||||||||||
not mapped to a field. The POJO field must be one of the following | ||||||||||||||
types: | ||||||||||||||
|
||||||||||||||
- `Document <{+api+}/apidocs/bson/org/bson/Document.html>`__ | ||||||||||||||
- `BsonDocument <{+api+}/apidocs/bson/org/bson/BsonDocument.html>`__ | ||||||||||||||
- ``Map<String, Object>`` | ||||||||||||||
|
||||||||||||||
.. seealso:: | ||||||||||||||
|
||||||||||||||
:ref:`BsonExtraElements Annotation Example <bsonextraelements-annotation-code-example>` | ||||||||||||||
- | Specifies the POJO field on which to deserialize all elements that are | ||||||||||||||
not mapped to a field. The POJO field must be one of the following | ||||||||||||||
types: | ||||||||||||||
| - `Document <{+api+}/apidocs/bson/org/bson/Document.html>`__ | ||||||||||||||
| - `BsonDocument <{+api+}/apidocs/bson/org/bson/BsonDocument.html>`__ | ||||||||||||||
| - ``Map<String, Object>`` | ||||||||||||||
| | ||||||||||||||
| See an example of a :ref:`BsonExtraElements Annotation Example <bsonextraelements-annotation-code-example>`. | ||||||||||||||
|
||||||||||||||
The following code snippet shows a sample POJO called ``Product`` that uses | ||||||||||||||
several of the preceding annotations. | ||||||||||||||
|
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.
S: Flows a bit better grammatically with the "a"