Hydrator aware interface

[ghunti]

Hi.

I've created a HydratorAwareInterface, that mimics the behaviour of the InputFilterAwareInterface.

This way we can avoid setting the hydrator on the form every time, we just make the object that we bind to the form aware of its own hydrator (with a simple getter and setter).

The patch uses the object hydrator if the form doesn't have one hydrator already, and this might be one of the points were you for sure have a better understanding if this is correct or not.

Thanks,

[ghunti]

@weierophinney It seems that i've made something on my local branch that broken this all up.
What should i do? Open a new pull request? Anyway, I've added the unit tests for the new Interface on commit https://github.com/ghunti/zf2/commit/b576cde361ef4933916eacd89dac4bd0169299df.

Sorry for all the mess

[ghunti]

@mpalourdio I'm not an expert, not i know very well how forms operate on the backend. I've just tried to mimic the InputFIlterAwareInterface without breaking current hydrator + form behavior.

Can you help me with an example?
Thanks

[ghost]

I don't have an precise example to provide you, and i don't even know if it's really possible. But imagine you have a form that is populated with 2 fieldsets. One fieldset is hydrated with the standard zf2 hydrator, and the other is hydrated by the doctrine hydrator from a doctrine entity. I was just wonderind if your interface could merge the 2 fieldsets each populated with a distinct hydrator. Maybe @weierophinney could best guide you with this particular case.

[macnibblet]

@ghunti When working on new features you must work in a new branch, else when you create a PR and update your master/develop it get filled with other peoples commits. So create a new branch and cherry-pick the commits you need and create a new pull request.

[ghunti]

Created a new pull request with the relevant commits on #4170