fix: throw BuildError during cds build to terminate build on errors #334
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #308
This PR ensures that errors during
cds buildproperly terminate the build process by throwing aBuildErrorinstead of silently logging errors.Changes
Core Fix (
lib/build.js)BuildErrorimport fromcds.buildbuild()method in try-catch and throwBuildErroron failure_writeResourcesFiles- let errors bubble up naturally_createProgressBar(),_countTotalFiles()helper methods)Tests
__tests__/unit/build.test.js): Updated to expect thrown errors instead of silent handling__tests__/integration/cds-build.test.js): Added 7 new test casesConfiguration
@cap-js/orddependency to enable build plugin discoverytest:integration:buildnpm scriptTest Results
Design Philosophy
Follows CAP Build Plugin design philosophy:
this.pushMessage(message, severity)- for non-fatal info/warningsthrow new BuildError(message)- for critical errors that should terminate the build