config.go should not depend on any libraries #107

New Issue

bvisness · 2023-05-19T01:39:09Z

bvisness commented

2023-05-19 01:39:09 +00:00

Our config.go requires you to import a couple libraries in order to provide log levels and such. This has proven to be a problem, because changing dependency versions sometimes causes config files to break. (Your individual config.go file is excluded from git, after all.) I think we should remove the need for third-party libraries from config.go so that we can avoid this friction in the future.

I realize that in some cases this comes at a small complexity or UX cost (nobody likes looking up docs to see what magic strings mean what), but I think we can mitigate it by just shipping our own enums in the config package.

Our config.go requires you to import a couple libraries in order to provide log levels and such. This has proven to be a problem, because changing dependency versions sometimes causes config files to break. (Your individual config.go file is excluded from git, after all.) I think we should remove the need for third-party libraries from config.go so that we can avoid this friction in the future. I realize that in some cases this comes at a small complexity or UX cost (nobody likes looking up docs to see what magic strings mean what), but I think we can mitigate it by just shipping our own enums in the config package.

Sign in to join this conversation.