PostHog / PostHog/posthog-unity
Implement feature flag cache and flag-called dedupe
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C#
- Stars
- 9
- Forks
- 5
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 8
Description
Summary
Implement canonical feature flag cache behavior and $feature_flag_called dedupe by flag value for the Unity SDK.
Expected behavior
Feature flag cache
- Successful flag loads cache flag values and payloads.
- Cached reads do not require another network request.
- Cached values/payloads are available to the public flag getter APIs.
- Cache is cleared when identity reset invalidates user-scoped flags.
$feature_flag_called dedupe
- Emit the first
$feature_flag_calledevent for a flag value. - Suppress duplicate events for the same flag and same value.
- Emit again when the flag value changes.
Specs
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with acceptance/private/feature-flag-cache.feature and acceptance/private/feature-flag-called-tracker.feature, then trace the Unity SDK’s flag-loading, identity-reset, and public flag getter entry points. Verify successful loads are reused and cleared on reset, and that $feature_flag_called is emitted once per flag value and again after a value change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, unity
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100