An issue (#46) was raised that describes an issue with not being able to store any kind of object in settings, since they will be unserialized to an object like __PHP_Incomplete_Class(...). While the default ValueSerializer can be overridden so that any objects can be unserialized properly, it may not always be desirable to create a custom class implementation of your own.
This PR adds a unserialize_safelist configuration option to allow you to specify which classes should be allowed to be unserialized. By default, we'll allow carbon date objects to be unserialized, but you are free to add more to the config.
An issue (#46) was raised that describes an issue with not being able to store any kind of object in settings, since they will be unserialized to an object like
__PHP_Incomplete_Class(...). While the defaultValueSerializercan be overridden so that any objects can be unserialized properly, it may not always be desirable to create a custom class implementation of your own.This PR adds a
unserialize_safelistconfiguration option to allow you to specify which classes should be allowed to be unserialized. By default, we'll allow carbon date objects to be unserialized, but you are free to add more to the config.