feat(asc): Add options merge algorithm for use by asconfig

[dcodeIO]

This is an attempt to solve the reconciliation problems encountered during #1238 by extending the existing options parser with a backtracking merge algorithm.

With this, we'd essentially start by parsing command line arguments, obtaining an initial set of options, then merge the project's asconfig.json if applicable and continue by merging parent project asconfig.jsons until we reach the end. Once done, we can add option defaults that we so far omitted.

The options enable and disable now have an additional mutuallyExclusive key indicating that whatever is newer in the respective other equalizes what's older. Does not affect the same level, but only merging a previous level.

There is a basic test in tests/cli/options.js, containing the following full usage test:

var result = optionsUtil.parse(["--enable", "a", "--disable", "b"], config, false); merged = optionsUtil.merge(config, result.options, { enable: ["b", "c"] }); merged = optionsUtil.merge(config, merged, { disable: ["a", "d"] }); optionsUtil.addDefaults(config, merged); assert.deepEqual(merged.enable, ["a", "c"]); assert.deepEqual(merged.disable, ["b", "d"]); assert.deepEqual(merged.other, ["x"]);

@jtenner Does this look like it'd help / work in all scenarios?

• I've read the contributing guidelines

[jtenner]

Wow this does the job. And it looks way more professional. Does this try to resolve asconfig files yet?

[MaxGraey]

Should we have also array of booleans?

 case "B": { if (!Array.isArray(value)) value = [ value ]; return value.map(Boolean); }

[dcodeIO]

We don't have these in other code paths, and I suspect that these won't be useful. At least I can't imagine an option where a [true, true, false, true ] would make a lot of sense.

[github-actions]

🎉 This PR is included in version 0.12.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀