Make caching more easily optional

[UmanShahzad]

Right now caching can be modified by a settings key to choose your own cache implementation.

However it should be easier to disable caching (it should really default to disabling, but that would be a breaking change); currently that requires creating a custom cache implementation which simply does nothing.

We can either create such an implementation that does nothing, or have a new key like cache_disabled and update cache-using code to check if the cache exists before using it.

[UmanShahzad]

Real use case for this is the Laravel SDK: it uses Laravel's own caching facilities already, and is apparently also using the PHP SDK's caching facility, which is completely redundant.

[coderholic]

it uses Laravel's own caching facilities already, and is apparently also using the PHP SDK's caching facility, which is completely redundant

Our laravel sdk? Shouldn't we just remove caching from that completely?

[UmanShahzad]

@coderholic Doing that would then require exposing the caching interfaces of the PHP SDK to the user who's working with the Laravel SDK, if the Laravel user wants control over caching at all. We could do that or wrap all those interfaces with new ones.

But more importantly, Laravel has some framework-level caching facilities, which presumably most users with caching going on are using, and the Laravel SDK-level caching is delegating to that. It's just more sensible to use Laravel's caching facilities when needing to cache stuff in a Laravel library of any kind, if we can do that. Presumably this is why the original author of the Laravel SDK implemented it that way; more idiomatic/etc for that particular framework.

[UmanShahzad]

Will be available in v2.3.0.