From 1f7e245e0be3237e644db649631bfda89ff8531a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ivar=20Conradi=20=C3=98sthus?= Date: Fri, 30 Oct 2020 09:22:01 +0100 Subject: [PATCH] fix: add docs for disabled variant closes #633 --- docs/feature-toggle-variants.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/feature-toggle-variants.md b/docs/feature-toggle-variants.md index 07fa353e26..a94ac13a0d 100644 --- a/docs/feature-toggle-variants.md +++ b/docs/feature-toggle-variants.md @@ -19,6 +19,17 @@ If the toggle is considered **enabled**, the Unleash client will select the corr If the toggle is considered **disabled** you will get the built-in `disabled` variant. +A json represntation of the empty variant will be the following: + +```json +{ + "name": "disabled", + "enabled": false +} +``` + +The actual representation of the built-in the client SDK will vary slighty, to honor best pratices in various languages. + > If you change the number of variants, it will affect variant allocations. This means that some of the users will be moved to the next variant. _Java SDK example:_