Bug: [Error] Call to undefined method Config\Mimes::__set_state() at ROOTPATH/writable/cache/FactoriesCache_config about codeigniter4 HOT 7 CLOSED

This is not a bug.

Important
Using this feature when the prerequisites are not met will prevent CodeIgniter from operating properly. Do not use this feature in such cases.

Read https://codeigniter4.github.io/CodeIgniter4/concepts/factories.html#prerequisite

from codeigniter4.

Use new Mimes() instead of config('Mimes').
Because config() is slow., there is no benefit to use config() for Mimes.

Also, Mimes extending BaseConfig makes the instantiation of Mimes very slow.
That is not the way to go.

from codeigniter4.

Either way, codeigniter factories does not work out-of-the-box with Config/Mimes.php, because it does not implement __set_state()

From your link to the docs: "By default, every Config class that is cached must implement __set_state() method."
So one would expect that the default implementation of Config/Mimes.php should implement __set_state() no?

from codeigniter4.

Either way, codeigniter factories does not work out-of-the-box with Config/Mimes.php, because it does not implement __set_state()

True, you cannot use Config caching with Config\Mimes.
It is intentional, because we don't need to cache it.

So one would expect that the default implementation of Config/Mimes.php should implement __set_state() no?

No.
It means, if you want to cache a Config class instance, the class must implement __set_state() method. Config\Mimes does not implement it, so you cannot cache it by default.

If the explanations in the user guide are not clear, please read the source code and understand how the Config caching works, and provide suggestions for improvement.

Config cache is an additional feature for experts who need any better performance.
We recommend that users who cannot troubleshoot on their own not use it.

Also, if you use caching, we recommend that you measure whether the caching is really effective.

from codeigniter4.

So, if Config/Mimes doesn't need to be cached, then why is it being included by default when enabling config caching?

Its common sense that if one enables a feature in the framework, one would expect it to work with its own default system files. I did not explicitly configure it to cache Config/Mimes, it does it on its own, out-of-the-box. Which breaks.

I would simply update the user guide to say: "Enabling this will not work by default, You have to manually override Config/Mimes and add __set_state method yourself"

from codeigniter4.

So, if Config/Mimes doesn't need to be cached, then why is it being included by default when enabling config caching?

It is not included by default. You intentionally did it by calling config('Mimes').

Enabling this will not work by default, You have to manually override Config/Mimes and add __set_state method yourself

This is incorrect. You should not cache it. In other words, you should not call config('Mimes'). If you do not call config(), Config/Mimes has nothing to do with Config Caching.

from codeigniter4.

Fair enough, makes sense. Thanks for your patience

from codeigniter4.