Conversation
Zaimwa9
force-pushed
the
feat/experiment-metadata
branch
2 times, most recently
from
September 16, 2026 08:09
e8b9dae to
b82e510
Compare
Zaimwa9
force-pushed
the
feat/experiment-metadata
branch
from
September 16, 2026 08:12
b82e510 to
95253d5
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Thanks for submitting a PR! Please check the boxes below:
docs/if required so people know about the feature.Changes
Core now sends
metadata.experiment { id, name, in_experiment }on/identitiesflags while the feature's experiment is running (Flagsmith/flagsmith#8532).IFlagsmithFeature.experiment?: { id, name, inExperiment }, lifted frommetadata.experiment.undefinedon older servers.getExperimentFlaganduseExperimentfire the exposure only wheninExperimentistrue, instead of guessing fromvariant. Flag data is still returned otherwise.metadata.experiment_idfor attribution.useFlagspropagatesexperimentthrough the React bindings.Release after Core (Flagsmith/flagsmith#8532) and Edge (Flagsmith/edge-api#719) are live: against older servers no flag carries
experiment, so no exposure is recorded.How did you test this code?
Jest: new
test/experiment.test.tsplus extended React event, variant and type tests, 131 tests passing.tscclean.Manual QA against staging once Core and Edge are deployed.