fix(@angular/build): include full metadata for AOT unit-testing #30366
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.
Include class metadata and JIT information in code built for development and/or test usage. All non-optimized builds will now contain this metadata (
optimization.scripts
is false). The Angular TestBed APIs require additional metadata for the Angular aspects of the application such as Components, Modules, Pipes, etc.TestBed may also leverage JIT capabilities during testing (e.g.,
overrideComponent
). To support all these TestBed usage scenarios both the underlyingsetClassMetadata
andsetNgModuleScope
class augmentation functions are now emitted when test metadata inclusion is enabled.