Custom Serialization handlers give an invalid result on top level about serializer HOT 5 CLOSED

You can do $visitor->setNavigator($navigator); in your handler if you are doing $navigator->accept on a subitem.

from serializer.

I don't see how that would be a solution to the problem stated in this issue report. The handler is supposed to return custom formatted data. In the case of a child item, this data is serialized. However, if the data is on the root level, the serializer returns NULL.

from serializer.

I'm experiencing the same problem.
The issue is that the visitor does not know about any root as long as you don't explicitly set one via $visitor->setRoot() or by "visiting" a value via $visitor->visit<Type>().

A workaround/hack is to normalize your object into an array and set this array as the root of the visitor:

public function serializeMyClassToJson(JsonSerializationVisitor $visitor, MyClass $obj, array $type, SerializationContext $context)
{
    $result = array(
        ...
    );

    $visitor->setRoot($result);

    return $result;
}

Besides working around the library, this of course does not work when the object of type MyClass is embedded in another object that should be serialized (without a custom handler that uses the same hack).

from serializer.

That's what the library also does https://github.com/schmittjoh/serializer/blob/master/src/JMS/Serializer/Handler/FormErrorHandler.php#L148-L150

from serializer.

Fixed in 2.0, now the visitors do not use an internal data representation, but the data are passed always back an forward to the graph navigator and serialized/deserialized with the new SerializationVisitorInterface::getResult($data) and DeserializationVisitorInterface::getResult($data) methods

from serializer.