Description
Bug Report or Feature Request (mark with an x
)
- [x] bug report -> please search issues before submitting
- [ ] feature request
@angular-devkit/architect-cli
Command
architect project:target --verbose
Versions
node --version
v8.11.4
npm --version
6.1.0
Angular CLI: 6.1.4
Node: 8.11.4
OS: win32 x64
Angular: 6.1.6
... compiler, compiler-cli, core
Package Version
------------------------------------------------------------
@angular-devkit/architect 0.7.5
@angular-devkit/build-angular 0.7.5
@angular-devkit/build-ng-packagr 0.7.5
@angular-devkit/build-optimizer 0.7.5
@angular-devkit/build-webpack 0.7.5
@angular-devkit/core 0.7.5
@angular-devkit/schematics 0.7.4 (cli-only)
@ngtools/json-schema 1.1.0
@ngtools/webpack 6.1.5
@schematics/angular 0.7.4 (cli-only)
@schematics/update 0.7.4 (cli-only)
ng-packagr 4.1.1
rxjs 6.2.2
typescript 2.9.2
webpack 4.9.2
Repro steps
architect project:target --verbose
where the target's builder's schema doesn't happen to have a verbose
property.
The log given by the failure
Data path "" should NOT have additional properties(verbose).
Desired functionality
Ability to utilize the code that calls createConsoleLogger()
passing verbose from cli args with out also passing that verbose arg to the target overrides, causing schema validation error.
Mention any other details that might be useful
If you simply don't pass verbose to target overrides then it would break when the schema does happen to have a verbose
property. Not sure what the best solution would be maybe try catch Architect.validateBuilderOptions() with and without verbose property present but not sure if that'd preformant