refactor(@angular/build): make buildTarget optional in unit-test builder #31368
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.
The
buildTarget
option in theunit-test
builder is now optional to streamline the user configuration.If the
buildTarget
option is not provided, the builder now defaults to using thebuild
target with thedevelopment
configuration for the current project. This change significantly reduces the boilerplate configuration needed inangular.json
for most projects, as the builder can now infer the correct build settings by convention.The builder's schema has been updated to reflect this change by removing
buildTarget
from the required properties and updating its description to document the new default behavior.