Mirrors/unleash.unleash
1
0
Fork 0
mirror of https://github.com/Unleash/unleash.git synced 2025-01-25 00:07:47 +01:00
Code Issues Projects Releases Wiki Activity

docs(chore): fix broken links to control_rollout

Browse Source
This commit is contained in:
Thomas Heartman 2022-01-14 14:20:28 +01:00 committed by Thomas Heartman
parent 775da4787b
commit 6d43b93be2
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/docs/sdks/java.md
View File

@ -57,7 +57,7 @@ Read more about the [Unleash architecture](https://www.unleash-hosted.com/articl
## Step 4: Provide Unleash Context {#step-4-provide-unleash-context} ## Step 4: Provide Unleash Context {#step-4-provide-unleash-context}
It is the client SDK that computes whether a feature toggle should be considered enabled or disabled for specific use request. This is the job of the [activation strategies](../user_guide/control_rollout), which are implemented in the client SDK. It is the client SDK that computes whether a feature toggle should be considered enabled or disabled for specific use request. This is the job of the [activation strategies](../user_guide/activation-strategies.md), which are implemented in the client SDK.
The activation strategies is an implementation of rules based on data, which you provide as part of the Unleash Context. The activation strategies is an implementation of rules based on data, which you provide as part of the Unleash Context.

2
website/docs/sdks/php.md
View File

@ -56,7 +56,7 @@ Read more about the [Unleash architecture](https://www.unleash-hosted.com/articl
## Step 4: Provide Unleash Context {#step-4-provide-unleash-context} ## Step 4: Provide Unleash Context {#step-4-provide-unleash-context}
It is the client SDK that computes whether a feature toggle should be considered enabled or disabled for specific use request. This is the job of the [activation strategies](../user_guide/control_rollout), which are implemented in the client SDK. It is the client SDK that computes whether a feature toggle should be considered enabled or disabled for specific use request. This is the job of the [activation strategies](../user_guide/activation-strategies.md), which are implemented in the client SDK.
The activation strategies is an implementation of rules based on data, which you provide as part of the Unleash Context. The activation strategies is an implementation of rules based on data, which you provide as part of the Unleash Context.

2
website/docs/user_guide/create-feature-toggle.md
View File

@ -32,7 +32,7 @@ The toggle is now created and ready to be used. The toggle does not have any met
## Step 4: Enable the feature toggle only for your boss! {#step-4-enable-the-feature-toggle-only-for-your-boss} ## Step 4: Enable the feature toggle only for your boss! {#step-4-enable-the-feature-toggle-only-for-your-boss}
The next step is to change the activation strategy to only target your boss. You can use the “userWithId”-strategy for that. Using the configuration shown below will only enable the feature toggle for “boss@company.com” and “me@company.com”. Thus, you can safely test your feature in production, without exposing it to your users. In [control roll-out](./control_rollout) with strategies we will go in to greater details on how to use activation strategies to gradually expose new features to your users. The next step is to change the activation strategy to only target your boss. You can use the “userIDs”-strategy for that. Using the configuration shown below will only enable the feature toggle for “boss@company.com” and “me@company.com”. Thus, you can safely test your feature in production, without exposing it to your users.
![Create a feature toggle](/img/create_feature_toggle_userIds.png) ![Create a feature toggle](/img/create_feature_toggle_userIds.png)