2 Commits

Author	SHA1	Message	Date
Nuno Góis	4adc977ba0	fix: properly handle flag resolver variants (#3808) ... Variants were not being properly handled in the `flag-resolver`: The fact that the default value of the variant is not falsy made it so we never asked the external flag resolver for the value. This also moves the logic from `Variant | undefined` to `Variant` where we use the `getDefaultVariant()` helper method to return us a [default variant](55274e4953/src/variant.ts (L37-L42)).	2023-05-18 17:04:55 +01:00
Nuno Góis	db61a8a40c	feat: message banner (variants) (#3788) ... - 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~~ (50ccf60893); - ~~Enterprise needs a PR that will follow soon~~; 	2023-05-18 09:38:59 +01:00