Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

case sensitive adjustments #1

Merged
merged 2 commits into from
Jan 25, 2021
Merged

case sensitive adjustments #1

merged 2 commits into from
Jan 25, 2021

Conversation

patrick-ogrady
Copy link

@patrick-ogrady patrick-ogrady commented Jan 25, 2021

Viper has opted to not support case-sensitive keys (https://github.com/spf13/viper#does-viper-support-case-sensitive-keys):

Does Viper support case sensitive keys?
tl;dr: No.

Viper merges configuration from various sources, many of which are either case insensitive or uses different casing than the rest of the sources (eg. env vars). In order to provide the best experience when using multiple sources, the decision has been made to make all keys case insensitive.

There has been several attempts to implement case sensitivity, but unfortunately it's not that trivial. We might take a stab at implementing it in Viper v2, but despite the initial noise, it does not seem to be requested that much.

You can vote for case sensitivity by filling out this feedback form: https://forms.gle/R6faU74qPRPAzchZ9

This PR applies changes described in a candidate PR (spf13#635) to optionally unlock this functionality.

@patrick-ogrady patrick-ogrady merged commit d8572fe into master Jan 25, 2021
@patrick-ogrady patrick-ogrady deleted the case-sensitive branch January 25, 2021 15:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant