From eadf1187595c1903ef79b8708972d3dd24efc7c8 Mon Sep 17 00:00:00 2001 From: Thomas Heartman Date: Wed, 24 Nov 2021 11:27:55 +0100 Subject: [PATCH] docs: delete old unleash-context doc. Similar to the activation strategy page: this seems to be deprecated and was not listed in the sidebar. There is also a newer, more fleshed out version that _does_ appear in the sidebar instead. --- website/docs/unleash-context.md | 21 --------------------- 1 file changed, 21 deletions(-) delete mode 100644 website/docs/unleash-context.md diff --git a/website/docs/unleash-context.md b/website/docs/unleash-context.md deleted file mode 100644 index 4d48709621..0000000000 --- a/website/docs/unleash-context.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -id: unleash_context -title: Unleash Context ---- - -To standardise a few activation strategies, we also needed to standardise the Unleash context, which contains fields that vary per request, required to implement the activation strategies. - -The unleash context is defined by these fields: - -- userId: String, -- sessionId: String, -- remoteAddress: String, -- properties: Map -- appName: String -- environment: String - -All fields are optional, but if they are not set you will not be able to use certain activation strategies. - -E.g., the `userWithId` strategy obviously depends on the `userId` field. - -The `properties` field is more generic and can be used to provide more arbitrary data to strategies. Typical usage is to add more metadata. For instance, the `betaUser` strategy may read a field from `properties` to check whether the current user is a beta user.