Skip to content

Commit d9143c2

Browse files
docs: add note about literal alias limitation (#401)
Track issue in viper: spf13/viper#1014 Co-authored-by: Ember Stevens <[email protected]>
1 parent b11a9d7 commit d9143c2

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

docs/ALIASES.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -35,6 +35,8 @@ var secondFeatureFlag = 'second-flag-key'
3535

3636
Aliases can be hardcoded using the `literal` type. This is intended to be used for testing aliasing functionality.
3737

38+
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).
39+
3840
Example hardcoding aliases for a couple flags:
3941

4042
```yaml

0 commit comments

Comments
 (0)