From 05adfb873127e9e8bdfb4f49560544e95bc63ec2 Mon Sep 17 00:00:00 2001 From: Matt Gibson Date: Wed, 20 Mar 2024 12:59:17 -0400 Subject: [PATCH] Clarify UserId property in context --- docs/contributing/feature-flags.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/contributing/feature-flags.md b/docs/contributing/feature-flags.md index 4c794ecf..4f26509a 100644 --- a/docs/contributing/feature-flags.md +++ b/docs/contributing/feature-flags.md @@ -98,7 +98,7 @@ debugging code.
The `flags.json` file can also define flags which respond to user context. Currently, only `UserId`and the `OrganizationId` of all organizations a user belongs to are included in our feature flagging context. The syntax for defining context-aware flags amounts to defining a `flag` object which specifies `variations` values and `rules` which are evaluated against the user context. A `fallthrough` object is also available to specify a default variation. Rules are represented by `segments`, which are defined in the same file. - a Feature flag may not appear in both the `flags` object and in the `flagValues` object. + a Feature flag may not appear in both the `flags` object and in the `flagValues` object. Note that UserId is referred to as `key` in the `clauses` object while defining a segment.