Skip to content
New issue

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

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

Already on GitHub? # to your account

AllKeys return key name in lower case which prohibits using camelCase in key name #1900

Open
3 tasks done
laplantePierre opened this issue Aug 9, 2024 · 2 comments
Open
3 tasks done
Labels
kind/bug Something isn't working

Comments

@laplantePierre
Copy link

Preflight Checklist

  • I have searched the issue tracker for an issue that matches the one I want to file, without success.
  • I am not looking for support or already pursued the available support channels without success.
  • I have checked the troubleshooting guide for my problem, without success.

Viper Version

1.19.0

Go Version

1.22

Config Source

Files

Format

TOML

Repl.it link

No response

Code reproducing the issue

for _, setting := range config.AllKeys() {
  element := config.Get(setting)
  fmt.Printf("setting = %s, element = %v\n", setting, element)
}

Expected Behavior

I have a variable defaultEngine but viper return in as defaultengine.

Actual Behavior

I have a variable defaultEngine but viper return in as defaultengine.

Steps To Reproduce

Create a variable in toml with camel case.

Additional Information

Would it be possible to have a function that return the key with the correct case ?

@laplantePierre laplantePierre added the kind/bug Something isn't working label Aug 9, 2024
Copy link

github-actions bot commented Aug 9, 2024

👋 Thanks for reporting!

A maintainer will take a look at your issue shortly. 👀

In the meantime: We are working on Viper v2 and we would love to hear your thoughts about what you like or don't like about Viper, so we can improve or fix those issues.

⏰ If you have a couple minutes, please take some time and share your thoughts: https://forms.gle/R6faU74qPRPAzchZ9

📣 If you've already given us your feedback, you can still help by spreading the news,
either by sharing the above link or telling people about this on Twitter:

https://twitter.com/sagikazarmark/status/1306904078967074816

Thank you! ❤️

@jwangace
Copy link

I support this change. this is problematic with us, as we have to deal with camelCase settings.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants