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.

Sign up for GitHub

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

Jump to bottom

The dependency problem #887

Open

sagikazarmark opened this issue Apr 9, 2020 · 0 comments

Milestone

Collaborator

sagikazarmark commented Apr 9, 2020

Viper has a huge number of dependencies.

This is the price paid for having a friendly API with all the features with zero configuration OOTB:

encoding/decoding from/into a large number of formats
reading from remote sources (etcd, firebase, etc)
having a filesystem abstraction library pulled in

In Viper 2, we should aim for lowering the number of dependencies. This is potentially a breaking change though.

This was referenced Apr 9, 2020

Rewrite the encoding layer as a library #888

Open

Create an abstraction for config loading #889

Open

andig mentioned this issue

[Viper 2] Make remote config optional #867

Closed

sagikazarmark mentioned this issue

for keep clean , remove provider ( remote ) to new repo #974

Closed

sagikazarmark mentioned this issue

Update go-ini dependency #1216

Merged

sagikazarmark added this to the v1.20.0 milestone

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment