Repository navigation
feat: Support getExperimentFlag, trackEvent and trackExposure methods - #322
flagsmithsmith[bot] wants to merge 4 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
|
…c v0.6.0 Spec v0.6.0 adds @events scenarios for getExperimentFlag, trackEvent and trackExposureEvent, plus a "Create the SDK client with events enabled" step. The SDK has supported these since 9.1.0, so the steps call the existing public API. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> (cherry picked from commit 6a108ea)
The getExperimentFlag step returned the feature name it was asked for, so the spec could not tell whether the SDK resolved the right flag. Report the evaluated flag's featureName instead. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The spec job was failing because spec v0.6.0+ added Changes
I ran spec v0.7.1 locally with Review effort: 1/5 🤖 Generated with Claude Code |
getExperimentFlag, trackEvent and trackExposure methods
|
Superseded by #324, which carries this pull request's work over to the SDK spec's latest version. |
Contributes to Flagsmith/sdk-spec#13