Skip to content

Commit

Permalink
Fixed some headers in README
Browse files Browse the repository at this point in the history
  • Loading branch information
robfletcher authored Jan 17, 2018
1 parent e9ec547 commit 367c297
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ User userDomain = Converter.create().toDomain(User.class, userProto);
```
Conversion of lists of objects is similar to single object conversion.

###@ProtoClass
### @ProtoClass
Annotation attibutes:

* *value* - required. Contains reference to protobuf message class.
Expand All @@ -51,7 +51,7 @@ Annotation attibutes:

If type of domain class field is complex (marked by **@ProtoClass**) protobuf-converter will convert this field value to related protobuf message (**DefaultMapperImpl.class** has to be specified as mapper attribute value)

###@ProtoField
### @ProtoField
Annotation attibutes:

1. *name* - optional. Related protobuf field name.
Expand All @@ -63,7 +63,7 @@ Use *name* attribute when domain class field name is different from name specifi

*converter* attribute is useful when domain class field type is different from protobuf message field type. E.g.: date value in the domain class is stored into **java.util.Date** and protobuf message uses int64(**java.lang.Long**). For field data tarnsformation you must specify **DateLongConverterImpl.class** as value of *converter* attribute. You can create own field type converter if you implement **TypeConverter** interface.

###Fields Ignore
### Fields Ignore

In case when you need to prevent transforming some domain fields values into protobuf message field values use **FieldsIgnore.class**.

Expand Down

0 comments on commit 367c297

Please sign in to comment.