Deduplicate feature flag called events
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
Research direction
Start with PostHog.FeatureFlags.Evaluations.enabled?/2 and get_flag/2, then read the sdk-specs feature-flag-called-tracker specification. Add tests covering the first read, duplicate read, changed value, context reset or reload, bounded memory, and concurrent access; done means repeated identical reads no longer emit duplicate events while changed evaluations emit again.
Written by the indexing model from the issue text.
Description
Summary
Deduplicate $feature_flag_called events for repeated flag reads.
Why
sdk-specs marks feature-flag-called-tracker as applicable to both client and server SDKs. The tracker prevents noisy repeated $feature_flag_called events when application code reads the same flag/value repeatedly.
Current status
PostHog.FeatureFlags.Evaluations.enabled?/2 and get_flag/2 record access and fire $feature_flag_called on each call. No dedupe tracker was found.
Suggested scope
- Add an internal tracker keyed by distinct ID + flag key + evaluated value/result.
- Emit
$feature_flag_calledon the first read of a value. - Suppress duplicate events for the same user/flag/value.
- Emit again when the value changes or the evaluation context is reset/reloaded.
- Keep memory bounded and concurrency-safe.
- Add tests for first read, duplicate read, and changed value.
References
- Dominant language
- Elixir
- Stars
- 66
- Forks
- 33
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 21
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from PostHog/posthog-elixir
-
enhancement feature/feature-flags
Difficulty 4/5 3-5 days Newbie friendliness 45/100
PostHog/posthog-elixir#215 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
PostHog/posthog-elixir#209 · 1 comment ·
Maintainers usually reply within 1 day
-
bug enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
PostHog/posthog-elixir#147 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 48/100
PostHog/posthog-elixir#146 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 45/100
PostHog/posthog-elixir#145 ·
Maintainers usually reply within 1 day
All issues in PostHog/posthog-elixir
Similar issues
-
@swmansion/popcorn: published .d.ts files lack extensions on relative imports, breaking moduleResolution node16/nodenextPossibly taken @Huyvux12 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
software-mansion/popcorn#929 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
ash-project/ash#3127 ·
Maintainers usually reply within 1 day
-
Bug: Table layout and date column are cut off on mobile screens on the Tournaments -> History pageOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
hexlet-codebattle/codebattle#2375 ·
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
wintermeyer/vutuv#2388 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100