Description of issue

Envars and argv provided to configue which utilize the 'separator' feature for nested config json objects do not transform the names of nested variables. So a argv or envar such as deep__four_two, should yield {deep: { fourTwo: '42' }} but instead yields {deep: { four_two: '42' }}.

Steps to reproduce. (Failing unit test)

        it('get nested, normalized value with underscores as a separator', (done) => {
            process.env.deep__four_two = '42';
            const configue = Configue({env: {normalize: true}, separator: '__'});
            // FIXIT: deep is { four_two: '42' } should be { fourTwo: '42' }
            expect(configue.get('deep.fourTwo')).to.equal('42');
            done();
        });

full example in my fork

I may poke around and see if I can contribute a fix unless one is obvious to you or this is expected behavior.

Thanks!

Issue description

Hi, I've been trying out configue for a project I'm working on. So far it's been good, thanks!

I did notice one thing that looks to be a corner case not covered by your tests. It appears that the normalize option and the env whitelist may not play well together. When I attempt to use both the configue.get returns 'undefined' for any whitelisted envars.

version

"configue": "^1.0.0-rc.4",

Failing Unit Test in Lab

 it('normalize works with the env whitelist option', (done) => {
    process.env.NO_SEP = 'no sep';
    const configue = new Configue({
      normalize: 'camelCase',
      env: {
        whitelist: ['NO_SEP']
      },
    });
    process.env.NO_SEP = undefined;
    expect(configue.get('noSep')).to.equal('no sep');
    done();
  });

Passing Unit Test in Lab

 it('normalize works by itself', (done) => {
    process.env.NO_SEP = 'no sep';
    const configue = new Configue({
      normalize: 'camelCase',
      env: {
        // whitelist: ['NO_SEP']
      },
    });
    process.env.NO_SEP = undefined;
    expect(configue.get('noSep')).to.equal('no sep');
    done();
  });

Hi all
I use HAPI JS and would like to use your package. Is it still maintained? I see that some version of dependency are not up to date, can you give a sign of life. I could help if you continue the project

Hi

I am wondering what sort of config this plugin is designed for. Plugins are called after hapi options are passed to its api so cannot be used to configure much with internals of hapi such as server options or server connections.

Thanks
Simon

Overview

If you are not aware yet, Hapi v17 is making the transition from callbacks to async/await, as well as deprecating some other rarely used functionality. This is a breaking change that may make your plugin no longer compatible with the Hapi API.

Changelog

Draft release notes can be found here: hapijs/hapi#3658

Target Release

The target release date for v17 is the beginning of November.

Tasks

• Reply to this to acknowledge that you are actively maintaining this module and are willing to update it
• Update plugin to be fully async/await compatible using the v17 branch from Hapi for testing

  Possible dev flow for updating

  • Clone Hapi
  • npm link within the Hapi repo
  • npm link hapi within your plugin repo
  • Your plugin will now be using v17 of Hapi branch for tests
• Release new major version of your plugin on npm. Please use a major version increment as this will be a breaking change and it would be terrible for it to sneak into current versions of Hapi.

Notes

• Support is being dropped for all versions of Node <8.0.0.
• Hapi v16 will continue to be supported for as long as there exists a Node LTS actively being supported that is not compatible with v17.
• Targeted release date is November 1st, 2017. Please try to have your plugin updated before then.