1
0
mirror of https://github.com/Unleash/unleash.git synced 2025-02-09 00:18:00 +01:00

fix: typo in strategy-constraints.md (#2115)

This commit is contained in:
Ivar Conradi Østhus 2022-09-29 19:26:14 +02:00 committed by GitHub
parent ec7e256140
commit 9ba441b9cf
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -13,7 +13,7 @@ Unleash 4.9 introduced a more comprehensive set of constraint operators. These r
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. Please see the [incompatibilities section](#incompatibilities) for more information. 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. Please see the [incompatibilities section](#incompatibilities) for more information.
::: :::
**Strategy constraints** are conditions that must be satisifed for an [activation strategy](../user_guide/activation_strategy) to be evaluated for a feature toggle. **Strategy constraints** are conditions that must be satisfied for an [activation strategy](../user_guide/activation_strategy) to be evaluated for a feature toggle.
With strategy constraints, you can: With strategy constraints, you can:
- roll out a feature **only to users in a specific region** - roll out a feature **only to users in a specific region**
- schedule a feature to be **released at a specific time** - schedule a feature to be **released at a specific time**