Repository navigation
feat: Support getExperimentFlag, trackEvent and trackExposure methods - #127
flagsmithsmith[bot] wants to merge 5 commits into
Conversation
Its entry in Flagsmith/sdk-spec's compatibility matrix at v0.7.1: `core or events or local-evaluation`.
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
Implements SDK spec v0.6.0's getExperimentFlag, trackEvent and trackExposureEvent. With `enable_events: true`, the client buffers events and sends them in batches to the Flagsmith events API (`events_api_url`). `get_experiment_flag` records an identity's exposure to the variant it was served when it is in the feature's running experiment, which flags now expose as `variant` and `experiment`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> (cherry picked from commit 3ec4437)
A slow or failing events API request held the flush lock while every further event past the buffer limit started another flush thread. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> (cherry picked from commit 2526c08)
- Stop running event processors at exit from one registry that a stopped processor leaves, instead of an at_exit block per start that kept every processor in memory. - Drop the identifier from the duplicate exposure debug log. - Give the accurate reason when get_experiment_flag skips an exposure because flags come from the environment document, which carries no experiment data. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> (cherry picked from commit f829d07)
|
The spec run was red because v0.7.1's compatibility matrix adds the I re-applied the earlier event tracking work:
The only conflict was in Checks run locally:
|
getExperimentFlag, trackEvent and trackExposure methods
Contributes to Flagsmith/sdk-spec#13