-
Notifications
You must be signed in to change notification settings - Fork 6
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
Support multiple config file types #172
base: main
Are you sure you want to change the base?
Conversation
Codecov Report
@@ Coverage Diff @@
## main #172 +/- ##
========================================
+ Coverage 0.00% 4.03% +4.03%
========================================
Files 1 5 +4
Lines 67 421 +354
========================================
+ Hits 0 17 +17
- Misses 67 401 +334
- Partials 0 3 +3
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
c67555b
to
9b1e889
Compare
Signed-off-by: Zsolt Rappi <[email protected]>
9b1e889
to
6315735
Compare
8109cca
to
ae10b6e
Compare
8a23efb
to
3e8e095
Compare
Signed-off-by: Zsolt Rappi <[email protected]>
3e8e095
to
7f95181
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
branch conflict needs to be resolved
Signed-off-by: Zsolt Rappi <[email protected]>
2d79b89
to
e368b40
Compare
Fixes #35
Dev notes
Why copied the encoding package instead of using Viper's Write methods? Unfortunately those methods have some problems and they are not reliable (A Viper contributor told me not to use them). They will be removed from Viper and after some discussion I decided to reuse their code. They also told me that the encoding package will be a separate project eventually, so as soon as that happens we can replace our encoding package with that.