config: expand comment [skip ci]
This commit is contained in:
parent
3a86905b14
commit
ac4cc4ad48
@ -86,9 +86,17 @@ func Load(conf string, isPath bool) (*Config, error) {
|
|||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
||||||
// only return now, one we had a chance to print the loaded config (as
|
// only return now (if err), after we've had the chance to print the loaded
|
||||||
// would be the case if the config adhered to the schema but our type
|
// config, as would be the case if the config *did* adhere to the schema imported
|
||||||
// definition above didn't - "don't know how to decode <nil> into ...")
|
// but app's Config type definition above didn't - "don't know how to
|
||||||
|
// decode <nil> into ..." is the most likely outcome in that case and it
|
||||||
|
// could be the product of (at least) three things:
|
||||||
|
// * completely wrong config not following the schema
|
||||||
|
// * config is following a newer schema than the app supports
|
||||||
|
// * config is following an older schema than the app supports
|
||||||
|
//
|
||||||
|
// NOTE: for the most part the only thing checked above would be adherence
|
||||||
|
// to config schema (apart from *some* value validation).
|
||||||
if err != nil {
|
if err != nil {
|
||||||
return nil, err
|
return nil, err
|
||||||
}
|
}
|
||||||
|
Loading…
Reference in New Issue
Block a user