Content
View differences
Updated by Jens Ulferts almost 9 years ago
Currently the representation/parsing of API resources is scattered over a number of representers and helper classes.
For WP there is e.g.:
- WorkPackageRepresenter
- WorkPackagePayloadRepresenter
- WorkPackageAttributeLinksRepresenter
For Query there is:
- QueryRepresenter
- QueryPayloadRepresenter
- QuerySerialization
The goal of the refactoring is to have a single representer for representation/parsing per resource:
- WorkPackageRepresenter
- QueryRepresenter
This change will reduce maintenance effort and increase the speed when implementing additional resources.
For WP there is e.g.:
- WorkPackageRepresenter
- WorkPackagePayloadRepresenter
- WorkPackageAttributeLinksRepresenter
For Query there is:
- QueryRepresenter
- QueryPayloadRepresenter
- QuerySerialization
The goal of the refactoring is to have a single representer for representation/parsing per resource:
- WorkPackageRepresenter
- QueryRepresenter
This change will reduce maintenance effort and increase the speed when implementing additional resources.