Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103756
MIME-Version: 1.0
Date: Thu, 17 Jan 2019 21:48:51 -0200
Message-ID: <CANA3Det3Cn2LAzcFPmVpP+ApgdtwDYrcnwuys8Gdo6CzRxLqBg@mail.gmail.com>
To: internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000fa2988057fb00960"
Subject: Unserializes, inheritance and allows_classes
From: marcospassos.com@gmail.com (Marcos Passos)

--000000000000fa2988057fb00960
Content-Type: text/plain; charset="UTF-8"

Hi internals,

Today I stumbled upon a limitation when implementing the unserialize method
of a serializable class which depends on an abstraction also serializable.
Currently, there is no way to unserialize an object specifying a parent
class in the allowed_classes option:

class SerializableBase implements \Serializable {
> }
> class SerializableChild extends SerializableBase {
> }
> class Foo implements \Serializable {
>    private $dependency;
>     public function __construct(SerializableBase $dependency) {
>         $this->dependency = $dependency;
>     }
>     public function serialize() : string {
>          return \serialize($this->dependency);
>     }
>    public function unserialize($data) : void {
>         $this->dependency = \unserialize($data, ['allowed_classes' =>
> SerializableBase::class]);
>    }
> }


Is this an intentional limitation?

- Marcos

--000000000000fa2988057fb00960--