feat: add support for configuration inheritance with extends

[alan-agius4]

Closes: #329

I'm submitting a...

[ ] Bug Fix
[x] Feature
[ ] Other (Refactoring, Added tests, Documentation, ...)

Checklist

• Commit Messages follow the Conventional Commits pattern
  • A feature commit message is prefixed "feat:"
  • A bugfix commit message is prefixed "fix:"
• Tests for the changes have been added

Description

Add support for configuration inheritance with extends

Closes: #329

Does this PR introduce a breaking change?

[ ] Yes
[x] No

[dherges]

Hi @alan-agius4,

if you ask my personal opinion: No. These kind of features led us in the past to the point where ng-packagr started: frustration in the face of thousands of lines of json configuration, possibly merging and overwriting values from one file with another.

Altogether, from the discussions in #190 and #278 I am happy with a ng-package.js file. People can implement configuration merging by providing a "dynamic js config".

[alan-agius4]

@dherges,

This below approach from #278 is also good; (didn’t see it before)

ng-package.js exporting the config (thru module.exports or exports default)

That said, the extends seems to be quite popular now a-days especially since it's also using by TypeScript in tsconfig.json, Ts Lint in tslint.json and many others. And the values will be overridden based on the hierarchy. Ie the first value found will override any other value for that property set in child files.

But at the end it's your call really :)

[github-actions]

This PR has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

_{This action has been performed automatically by a bot.}