Demand option of nested config file parameters is not working

The following example will always fail, if the parameter --foo.bar is not passed through a config file:

const args = require("yargs")
    .config("c")
    .options("foo.bar", {
        demandOption: true,
    })
    .argv;

console.log(args);

config.json:

{
    "foo": {
        "bar": "asdf"
    }
}

If demandOption is not set, the output is, as expected { _: [], c: 'config.json', foo: { bar: 'asdf' }, '$0': 'index.js' }. If it is set the following error is returned:

Missing required argument: foo.bar

[bcoe]

@JoshMcCullough oh no worries, I didn’t take it as such.

I’ve just been dragging my feet on changes to object syntax, because I know if it was done on in a one off, feature by feature, implementation, we’d spend the next 5 years finding parts of the parser where we’d missed supporting it.

Need to figure out some sort of pre-processing step that hits everything at once.

[JoshMcCullough]

Gotcha. My use of yargs is very limited, so I didn’t mean to trivialize this issue/fix, though I already realize that I did. 😃