Feature suggestion: nested specifications about envconfig HOT 4 CLOSED

What would an example specification struct look like? (i.e. What is the use case for this?)

from envconfig.

My company is currently using JSON files to store configuration data and many of our "specifications" have a lot of levels. We are giving up on this way but we don't want to rewrite everything to fit on just one level.

Some test code I wrote to cover this implementation:

type Specification struct {
    // ...
    Nested                       NestedSpecification
}

type NestedSpecification struct {
    SomeValue string
}

func TestNestedSpecification(t *testing.T) {
    var s Specification
    os.Clearenv()
    os.Setenv("ENV_CONFIG_NESTED_SOMEVALUE", "foo")
    if err := Process("env_config", &s); err != nil {
        t.Error(err.Error())
    }

    if s.Nested.SomeValue != "foo" {
        t.Errorf("expected %q, got %q", "foo", s.Nested.SomeValue)
    }
}

from envconfig.

Definitely seems like a valid use case and a useful feature! 👍

from envconfig.

Implemented in #12

from envconfig.