env VS viper

How is this compared to https://github.com/caarlos0/env

One could consider using https://github.com/caarlos0/env instead of the hand-woven

These are a few reasons my team is using https://github.com/caarlos0/env

Consider something like this library that allows loading of environment variables into a struct.

The pattern with using struct tags was inspired by the eminent module env (https://github.com/caarlos0/env).

https://github.com/caarlos0/env.

How does it compare with https://github.com/caarlos0/env ?

I also have been using https://github.com/caarlos0/env in all projects since that was the one which I used in first project.

5. Viper

Managing configurations efficiently is a cornerstone of building scalable and maintainable software. In Go, the Viper package 🐍 stands out as a robust solution for managing application configurations. With support for multiple file formats, environment variables, and seamless unmarshaling to structs, Viper simplifies configuration management for modern applications.

- Terminal-Based Workflow: CREV is a CLI tool, removing the need to switch between your editor and the browser.

I have written the CREV CLI tool in Go as I was interested in learning the language and I heard many good things about it’s efficiency and speed. I used https://github.com/spf13/cobra to manage the CLI commands and [Viper](https://github.com/spf13/viper) for handling configurations. This is the first project I have done with Go but I find the language interesting and the Go routines also help with reading in your entire codebase. For the code reviews themselves I use google cloud functions which invoke GPT-4o (am also planning to add Claude 3.5 and GPT-o1).

I’d love to hear your feedback—whether it’s ideas for new features or reasons why you believe this tool is useful or useless to you. I am using it daily so it at least solved my own problem :)

Environment variables: using Viper

Once environment variables are setup we need load them into our project. For this this i will use viper

The code uses Viper to load configuration files in the application.

github.com/spf13/viper

Instead of directly accessing environment variables with os.Getenv(), integrating a configuration handler like viper might make it maintainable.