Laravel 13 Caching Restrictions

[mikebronner]

Hi @mikebronner!

Do I read it properly that you serialize and unserialize whole classes in the cache?

Laravel 13 says it's not recommended and if used, the class must be added to exceptions:
https://laravel.com/docs/13.x/upgrade#cache-serializable_classes-configuration

If this is indeed the case, maybe it would be good not to serialize the whole classes, but just to save the cached data as json/array?

Originally posted by @boryn in #207 (comment)

[mikebronner]

@boryn Thanks for pointing that out! This was much tougher to solve than it initially appears, please see the new config option.

[boryn]

@mikebronner I’m impressed by how fast you react to reported issues!!!

[mikebronner]

@boryn thanks :) I wasn't aware of this change in Laravel 13, so when you brought it up I wanted to make sure that the package was working correctly. We have to cache the full models because the toArray() methods on the models of some of the providers do not export all values, so data is being lost and we would not be able to rehydrate the models completely when reading from cache.