mirror of
https://github.com/Unleash/unleash.git
synced 2024-10-18 20:09:08 +02:00
db61a8a40c
-
https://linear.app/unleash/issue/2-546/fetch-the-payload-from-a-real-feature-flag
-
https://linear.app/unleash/issue/2-547/adapt-ui-to-use-the-feature-flag-information-were-fetching
Tackles the 2 tasks above.
Adapts our `FlagResolver` logic to support variants, so we can use them
for our message banner project but also anything else in the future.
Also adapts MessageBanner to the new logic.
- Add support for variants in `FlagResolver`;
- Adapt `MessageBanner` to a variants flag;
- Adds `sticky` support for the `MessageBanner`;
- Adds our first variants flag to `uiConfig` and `experimental`:
`messageBanner`;
- Adds a `variant-flag-schema` to make it easy to represent the variant
output that we specify in `uiConfig`;
- Adapts `experimental` to be able to represent default variants while
still maintaining type safety;
- Adds helpers to make it easy to use variants in our project, such as
`getVariantValue` and the `useVariant` hook;
- Adapts and adds new tests in `flag-resolver.test.ts`;
### Notes
- ~~The `as PayloadType` assertions need
https://github.com/Unleash/unleash-client-node/pull/454 since it
includes https://github.com/Unleash/unleash-client-node/pull/452~~
(
|
||
|---|---|---|
| .. | ||
| addons | ||
| admin | ||
| application | ||
| archive | ||
| changeRequest | ||
| common | ||
| context | ||
| demo | ||
| environments | ||
| events | ||
| feature | ||
| feedback | ||
| layout | ||
| loginHistory | ||
| maintenance | ||
| menu | ||
| playground/Playground | ||
| project | ||
| providers | ||
| segments | ||
| splash | ||
| strategies | ||
| tags | ||
| user | ||
| App.tsx | ||
| InitialRedirect.tsx | ||