You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There has some been discussion recently about the behavior of the in memory cache within the SDKs. Would you mind telling me a bit more about your use case so we can capture that need in future discussions?
The client used by our Rails app is instantiated with use_ldd: true. We have code in our app that was intended to clear the in-memory cache. There was some confusion and it was believed that it could be cleared calling flush on the client. While looking into another issue I realized that flush wasn't clearing the cache as originally thought and was looking for a way to actually clear it without extending SDK.
Is your feature request related to a problem? Please describe.
When in
ldd
mode, I would like to be able to manually clear the in-memory cache rather than wait for the expiration.Describe the solution you'd like
The ability to call
client.clear_cache
orstore.clear_cache
or something to that effect which would ultimately call LaunchDarkly::ExpiringCache#clear.Describe alternatives you've considered
Given the encapsulation of the cache, the only option currently seems to be to close the current client and initialize a new one.
The text was updated successfully, but these errors were encountered: