From 4306836511e5905e37d4a595071c5ef235167a1c Mon Sep 17 00:00:00 2001 From: Thomas Heartman Date: Fri, 1 Apr 2022 10:24:08 +0200 Subject: [PATCH] docs: Add .NET SDK to list of SDKs that crash on 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 ee8f3615ead..4b4376b498f 100644 --- a/website/docs/advanced/strategy-constraints.md +++ b/website/docs/advanced/strategy-constraints.md @@ -183,7 +183,7 @@ It's important that you use an up-to-date client SDK if you're using the advance If you use the new constraints with old SDKs, here's how it'll affect _some_ of the SDKs (the list is not exhaustive): - The Node.js and Go client SDKs will ignore the new constraints completely: the constraints will not affect the toggle's status. - The Python client SDK will evaluate the toggle to false, as it cannot evaluate the constraint successfully. -- The Ruby and PHP SDKs raise exceptions if the provided operator is not `IN` or `NOT_IN`. +- The .NET, Ruby, and PHP SDKs raise exceptions if the provided operator is not `IN` or `NOT_IN`. Please inspect the [SDK compatibility table to see which version of your preferred SDK introduced support for this feature](../sdks/index.md#strategy-constraints).