config-designing

What problem does it solve?

Go projects often struggle to pick a configuration pattern that cleanly separates serializable config from runtime options. This guide helps you decide between Config struct + Options, Options Only, and go-config for applications, ensuring scalable, maintainable design.

Core Features & Use Cases

• Decision patterns for library design and application wiring.
• Guidance on migration from older constructors to Config + New(cfg, opts...).
• Clear rules for zero-value defaults and separation of concerns.

Quick Start

Choose a pattern and implement it by creating a Config struct with a New(cfg, opts...) signature, or use an Options-Only constructor for runtime dependencies.