[WIP] Hydrator and resource serialization #39
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I want to do correctly the hydration stuff, both for extraction and hydration.
Here are the features that we need to implement properly:
At some point, those objects would use the resource metadata that contains various information from mapping (for instance how a given association should be represented). So we most likely have a custom Paginator class that extends Zend\Paginator and hold metadata or something like that.
@Ocramius , is this something you could work on ? I'd be happy to update the current doc to reflect my latest changes so that you can use it more quickly.