check if the data implements SerializationHandlerInterface and in that ca

[lsmith77]

check if the data implements SerializationHandlerInterface and in that case call it before going through the custom handlers (guess a similar change would need to be made for deserialization)

addresses #21

[schmittjoh]

Could you move this to the GraphNavigator.php (this avoids code duplication)? Also, it should have a small test.

[lsmith77]

ok .. will have a look.

[lsmith77]

done

[lsmith77]

hmm i fear that with this change deserialization might be broken .. if i read it properly GraphNavigator.php is used in both cases? does $isSerialization tell me inside the accept() method if i am running in serialization or deserialization mode?

[lsmith77]

i have merged your changes and fixed the code accordingly .. the tests pass now.

[schmittjoh]

Are you sure you committed everything? I got some failures here.

[lsmith77]

ooppss ... ran the tests so often that i forgot that i had a filter set .. will have a look.

[lsmith77]

done

[schmittjoh]

I've turned this off by default as it is mainly to ease migration, but otherwise merged everything.

[lsmith77]

Hmm .. I dont think its mainly for migration. I think this is an important feature in case someone has a wide range of classes that need to be serialized with custom logic that is simply not feasible to do in a single handler and that would otherwise lead to too many custom handlers. but its easy enough to enable for those users, so its all good i guess :)