Open discentem opened 9 months ago
👋 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! ❤️
Preflight Checklist
Viper Version
1.17.0
Go Version
1.21
Config Source
Files
Format
JSON
Repl.it link
https://replit.com/@kurtzbrandon/viperreadinconfigbug
Code reproducing the issue
Expected Behavior
The second call to
load()
withcreateWithoutAbsolute
is expected to fail but it should not mention my real OsFs in the error message. Instead I expect the error message to only reference the in memory filesystem. It seems viper.ReadInConfig() has some fallback behavior maybe? If such behavior exists as a feature, fallback should be off by default.Actual Behavior
The error message from
viper.ReadInConfig()
is referencing filepaths on my real OsFs even though I told viper to only read from in-memSteps To Reproduce
No response
Additional Information
No response