From d9143c2a5ff8f5631d316d0e2331eb5b29dc6540 Mon Sep 17 00:00:00 2001 From: Jaz White Date: Wed, 18 Oct 2023 15:52:49 -0400 Subject: [PATCH] docs: add note about literal alias limitation (#401) Track issue in viper: https://github.com/spf13/viper/issues/1014 Co-authored-by: Ember Stevens <79482775+ember-stevens@users.noreply.github.com> --- docs/ALIASES.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/ALIASES.md b/docs/ALIASES.md index 1010ad4c..6fe8f2ad 100644 --- a/docs/ALIASES.md +++ b/docs/ALIASES.md @@ -35,6 +35,8 @@ var secondFeatureFlag = 'second-flag-key' Aliases can be hardcoded using the `literal` type. This is intended to be used for testing aliasing functionality. +Note that literal aliases are limited to flag keys using lowercase letters only, due to a limitation of a dependency LaunchDarkly uses to parse the configuration file. [You can track the issue here](https://github.com/spf13/viper/issues/1014). + Example hardcoding aliases for a couple flags: ```yaml