Skip to content

Commit ce156c1

Browse files
committed
DATAMONGO-1250 - Fixed inline code formatting in reference docs.
1 parent 434e553 commit ce156c1

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/main/asciidoc/reference/mongodb.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2013,7 +2013,7 @@ class MyConverter implements Converter<Person, String> { … }
20132013
class MyConverter implements Converter<String, Person> { … }
20142014
----
20152015

2016-
In case you write a `Converter` whose source and target type are native Mongo types there's no way for us to determine whether we should consider it as reading or writing converter. Registering the converter instance as both might lead to unwanted results then. E.g. a `Converter<String, Long>` is ambiguous although it probably does not make sense to try to convert all `String`s into `Long`s when writing. To be generally able to force the infrastructure to register a converter for one way only we provide `@ReadingConverter` as well as `@WritingConverter` to be used at the converter implementation.
2016+
In case you write a `Converter` whose source and target type are native Mongo types there's no way for us to determine whether we should consider it as reading or writing converter. Registering the converter instance as both might lead to unwanted results then. E.g. a `Converter<String, Long>` is ambiguous although it probably does not make sense to try to convert all `String` instances into `Long` instances when writing. To be generally able to force the infrastructure to register a converter for one way only we provide `@ReadingConverter` as well as `@WritingConverter` to be used at the converter implementation.
20172017

20182018
[[mongo-template.index-and-collections]]
20192019
== Index and Collection management

0 commit comments

Comments
 (0)