From 84f44c0396abfd54f7cf3000b499728e28e0c058 Mon Sep 17 00:00:00 2001 From: Thomas Heartman Date: Thu, 17 Mar 2022 11:45:40 +0100 Subject: [PATCH] docs: Add note saying that some SDKs will crash with new operators. --- website/docs/advanced/strategy-constraints.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/advanced/strategy-constraints.md b/website/docs/advanced/strategy-constraints.md index 805e7b8aad..2bfe519b89 100644 --- a/website/docs/advanced/strategy-constraints.md +++ b/website/docs/advanced/strategy-constraints.md @@ -10,7 +10,7 @@ Unleash 4.9 introduced a more comprehensive set of constraint operators. These r ::: :::caution undefined behavior -When using _advanced strategy constraints_ (any operator that isn't `IN` or `NOT_IN`), *make sure your client SDK is up to date* and supports this feature. For older versions of the client SDKs we **cannot guarantee** any specific behavior: the constraints may evaluate to `false` or they may evaluate to `true`. +When using _advanced strategy constraints_ (any operator that isn't `IN` or `NOT_IN`), *make sure your client SDK is up to date* and supports this feature. For older versions of the client SDKs we **cannot guarantee** any specific behavior: the constraints may evaluate to `false`, they may evaluate to `true`, or the client may raise an exception (as in the case of the **Ruby SDK** prior to **version 4.1.0**). ::: **Strategy constraints** are conditions that must be satisifed for an [activation strategy](../user_guide/activation_strategy) to be evaluated for a feature toggle.