mirror of
https://github.com/Unleash/unleash.git
synced 2025-09-10 17:53:36 +02:00
chore: undeprecate custom strategies (#9939)
This commit is contained in:
parent
94c73bbc5d
commit
3a37386449
@ -122,12 +122,11 @@ class StrategyController extends Controller {
|
|||||||
permission: CREATE_STRATEGY,
|
permission: CREATE_STRATEGY,
|
||||||
middleware: [
|
middleware: [
|
||||||
openApiService.validPath({
|
openApiService.validPath({
|
||||||
deprecated: true,
|
|
||||||
tags: ['Strategies'],
|
tags: ['Strategies'],
|
||||||
operationId: 'createStrategy',
|
operationId: 'createStrategy',
|
||||||
summary: 'Create a strategy',
|
summary: 'Create a strategy',
|
||||||
description:
|
description:
|
||||||
'Creates a custom strategy type based on the supplied data. Custom strategies are deprecated and should not be used. Prefer using built in strategies with constraints instead.',
|
'Creates a custom strategy type based on the supplied data.',
|
||||||
requestBody: createRequestSchema('createStrategySchema'),
|
requestBody: createRequestSchema('createStrategySchema'),
|
||||||
responses: {
|
responses: {
|
||||||
201: resourceCreatedResponseSchema('strategySchema'),
|
201: resourceCreatedResponseSchema('strategySchema'),
|
||||||
|
@ -158,14 +158,12 @@ If the constraint uses a standard Unleash context field, set the context field t
|
|||||||
|
|
||||||
Unleash SDKs expect all context values to be strings. If you use an operator that acts on non-string values, such as [numeric operators](#numeric-operators) or [date and time operators](#date-and-time-operators), the SDKs attempt to convert the string into the expected type. If the conversion fails, the constraint evaluates to `false`.
|
Unleash SDKs expect all context values to be strings. If you use an operator that acts on non-string values, such as [numeric operators](#numeric-operators) or [date and time operators](#date-and-time-operators), the SDKs attempt to convert the string into the expected type. If the conversion fails, the constraint evaluates to `false`.
|
||||||
|
|
||||||
|
## Custom activation strategies
|
||||||
|
|
||||||
|
[Custom activation strategies](/reference/custom-activation-strategies)
|
||||||
|
|
||||||
## Predefined strategy types
|
## Predefined strategy types
|
||||||
|
|
||||||
:::caution
|
:::caution
|
||||||
[Predefined strategy types](/reference/predefined-strategy-types), such as UserIDs, IPs, and Hosts are a legacy implementation. Please use the default strategy with constraints to achieve your desired targeting.
|
[Predefined strategy types](/reference/predefined-strategy-types), such as UserIDs, IPs, and Hosts are a legacy implementation. Please use the default strategy with constraints to achieve your desired targeting.
|
||||||
:::
|
:::
|
||||||
|
|
||||||
## Custom activation strategies
|
|
||||||
|
|
||||||
:::caution
|
|
||||||
[Custom activation strategies](/reference/custom-activation-strategies) are deprecated. Please use the default strategy with constraints.
|
|
||||||
:::
|
|
@ -2,10 +2,6 @@
|
|||||||
title: Custom Activation Strategies
|
title: Custom Activation Strategies
|
||||||
---
|
---
|
||||||
|
|
||||||
:::caution
|
|
||||||
[Custom activation strategies](/reference/custom-activation-strategies) are deprecated. Please use the [default activation strategy](/reference/activation-strategies) with constraints.
|
|
||||||
:::
|
|
||||||
|
|
||||||
**Custom activation strategies** let you define your own activation strategies to use with Unleash. When the [built-in activation strategies](../reference/activation-strategies.md) aren't enough, custom activation strategies are there to provide you with the flexibility you need.
|
**Custom activation strategies** let you define your own activation strategies to use with Unleash. When the [built-in activation strategies](../reference/activation-strategies.md) aren't enough, custom activation strategies are there to provide you with the flexibility you need.
|
||||||
|
|
||||||
Custom activation strategies work exactly like the built-in activation strategies when working in the admin UI.
|
Custom activation strategies work exactly like the built-in activation strategies when working in the admin UI.
|
||||||
|
Loading…
Reference in New Issue
Block a user