Allow providing a custom implementation of FeatureRequesterCache

[mattford]

Is your feature request related to a problem? Please describe.

Currently the SDK provides an an implementation of FeatureRequesterCache based on APCU. I have a Laravel app which has it's own caching system, I can easily create an implementation of the interface to work with Laravel's caching however as far as I can tell there is no way to tell the SDK to use it.

Describe the solution you'd like

Add a way to provide an implementation of FeatureRequesterCache, for example the $options array could have a cacheProviderClass key, or the LDClient could have a method setCache

Describe alternatives you've considered

I don't believe this is possible to do currently without either forking the SDK or by doing some Reflection stuff to swap in the implementation to the private _cache property, which doesn't seem a good idea in production code.

[keelerm84]

@mattford thank you for raising this issue. It seems like something we should be able to support. I am taking a look now and will let you know once we have a resolution for you.

Thanks!

[keelerm84]

@mattford this was released in 6.7.0 this morning. Please let me know if you have any questions or run into any issues!