Let's say, for fun, I have good reasons to serialize an object. When I then have good reasons to unserialize that object, I'm getting dynamic property deprecation warnings. Is this just the way of the world now or is there something I'm missing? I don't "own" the class, so I can't easily mark dynamic properties as allowed before serializing (and I'm not even sure that would work).
@EdGrosvenor *could* you own it?
#[AllowDynamicProperties]
class mine extends theirs { }
(or adding the property)
and then using your copy only?
but also yes iirc only stdClass or those with __get/set is gonna be silent about it.
