Serializable Uuid's.

[ramsey]

Serializable Uuid's.

[ramsey]

What is the output corruption you're seeing?

I gave some thought to this when I accepted the JsonSerializable pull request, but I couldn't figure out the value of it, since the behavior would be confusing.

If we serialize it to a string representation of a UUID, what information is available in the serialized representation to tell PHP to unserialize it back into a Ramsey\Uuid\Uuid object? It seems to me the engine would see it as a serialized string (despite having an unserialize method on the class) and unserialize it into a PHP string, which is not what I would expect.

If my understanding of how this would work is wrong, let me know.

[frankdejonge]

@ramsey the string representation output by the serialize method is used for the output rather than replacing the output, so the output is something like:

"C:16:"Ramsey\Uuid\Uuid":36:{daf8aaf8-be7a-46ed-88ae-41221f36ba11}"

So in practice a this:

$oldUuid = Uuid::uuid4();
$uuid = Uuid::fromString($oldUuid->toString());
$oldUuid->equals($uuid); // true

Will be the same as:

$oldUuid = Uuid::uuid4();
$uuid = unserialize(serialize($oldUuid);
$oldUuid->equals($uuid); // true

Hope this clears it up.

[ramsey]

Interesting. Please proceed. :-)