Repository navigation
feat: Support getExperimentFlag, trackEvent and trackExposure methods - #72
flagsmithsmith[bot] wants to merge 3 commits into
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
Its entry in Flagsmith/sdk-spec's compatibility matrix at v0.7.1: `core or events or local-evaluation`.
Implements SDK spec v0.7.1's `@events` capability: - `Flagsmith.Client.get_experiment_flag/4` gets an identity's flag and, when the identity is enrolled in a running experiment on an enabled feature, sends a `$flag_exposure` event valued with the variant served. - `Flagsmith.Client.track_event/3` and `track_exposure_event/3` send events to Flagsmith's events API. - Events are buffered per environment key by a supervised processor and sent in batches on an interval, when the buffer fills, and on shutdown; failed batches are kept and retried. - Flags from the identities API now carry their `variant` and `experiment` metadata. - New options: `enable_events`, `events_api_url` and `events_flush_interval_milliseconds`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> (cherry picked from commit 9caa72a)
|
Re-applied 9caa72a (experiment flags, event and exposure tracking) as d2d51a5. This implements the The
Checked locally: This comment was written by an AI agent (OpenHands). |
getExperimentFlag, trackEvent and trackExposure methods
Contributes to Flagsmith/sdk-spec#13