In v15.4.1, when passing in nested environment variables, the case of the nested fields would remain how they were defined.
e.g.
const argv = yargs.env('CONFIG')....
and defining an environment variable like CONFIG_some__nested__camelCase__id=foo.
In v15.4.1 this would parse as {some: {nested: {camelCase: {id: 'foo'}}}}
In the latest 16.2 release, I am seeing: {some: {nested: {camelcase: {id: 'foo'}}}}
Note the camelCase field is now lowercased.
I can provide a repro example, but wanted to get the issue out here, in case this was already known (either as a regression or as new behavior). Thanks!
In
v15.4.1, when passing in nested environment variables, the case of the nested fields would remain how they were defined.e.g.
const argv = yargs.env('CONFIG')....and defining an environment variable like
CONFIG_some__nested__camelCase__id=foo.In
v15.4.1this would parse as{some: {nested: {camelCase: {id: 'foo'}}}}In the latest
16.2release, I am seeing:{some: {nested: {camelcase: {id: 'foo'}}}}Note the
camelCasefield is now lowercased.I can provide a repro example, but wanted to get the issue out here, in case this was already known (either as a regression or as new behavior). Thanks!