defaults behave like overrides if specified before other stores about nconf HOT 5 OPEN

Sorry to be a necromancer with this issue, but the whole order of how nconf loads values seems counterintuitive. It's probably way too late to have anything change at this point, but I would expect things to work more like CSS definitions or the spread operator with javascript objects (where the last value specified for a given key takes precedence). Something similar (in terms of order) to below:

const config = {
  ...defaults,
  ...fileA,
  ...fileB,
  ...args,
  ...overrides,
}

nconf basically works the exact opposite of the above, with the first value for a specified key overriding any later entry. It's certainly not impossible or even hard to use this way, but it does seem like most other resolvers take a later value over an earlier one.

from nconf.

👍

from nconf.

This!

I ran into this today. And still see not workaround for this. For my tests i would like to declare some defaults to use, so my tests are always running with fixed values.

from nconf.

The 'workaround' is to just put defaults at the very end -- just like in the example in the readme. That way, overrides are unchangable, then env and args are applied, then the config files, and finally defaults. These scheme has worked great for me! Btw, looking at the code you can see that defaults and overrides are the same thing.

from nconf.

👍

from nconf.