feat: New IFeatureFlagCache interface and implementations #12
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
HttpContextFeatureFlagCache
implementsIFeatureFlagCache
and retrieves feature flags fromHttpContext.Items
if they exist. Otherwise it calls the/decide
endpoint. Items are cached perdistinctUserId
, which in most cases will map 1-1 to an HTTP request.If the
HttpContext
is not available, then feature flags are always requested.By default,
PostHogClient
will use aNullFeatureFlagCache
with no caching. When registeringPostHogClient
using the methods provided for ASP.NET Core, that's replaced with anHttpContextFeatureFlagCache
.Fixes #11