Preflight Checklist
- [X] I have searched the issue tracker for an issue that matches the one I want to file, without success.
Problem Description
The currenl watch function is kinda weak, user cannot know what changed exactly and cannot reject any invalid changes.
Proposed Solution
We can implement a unifed Event that contains more infromation: new and old version of the config content, for both remote source and local file source.
Alternatives Considered
We can allow user to register the schema, validation funcs before read the configs so that user can know whether the config valid immediately. With the validation function, we can reject the unexpected changes on the config also.
Additional Information
What do you think of these feature? I'm glad to contribute codes to this project to implement them if you think they are good ideas.
Comment From: github-actions[bot]
👋 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! ❤️
Comment From: github-actions[bot]
Issues with no activity for 30 days are marked stale and subject to being closed.