Skip to content

Commit

Permalink
docs: add note about literal alias limitation (#401)
Browse files Browse the repository at this point in the history
Track issue in viper: spf13/viper#1014

Co-authored-by: Ember Stevens <[email protected]>
  • Loading branch information
jazanne and ember-stevens authored Oct 18, 2023
1 parent b11a9d7 commit d9143c2
Showing 1 changed file with 2 additions and 0 deletions.
2 changes: 2 additions & 0 deletions docs/ALIASES.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down

0 comments on commit d9143c2

Please sign in to comment.