Repository navigation
Conversation
Report a component whose selector matches <ng-container> or <ng-template> as an error. Neither element can host a component, so the template fails when it renders: dev mode throws an assertion, and production mode throws a DOM error. BREAKING CHANGE: A component on <ng-container> or <ng-template> is now an error A component whose selector matches <ng-container> or <ng-template> now fails to compile with NG8032. Such a template already failed when it rendered. Use an element that matches the component's selector instead.
This was referenced Nov 8, 2026
Owner
Author
|
Superseded by the upstream PRs angular#71882, angular#71883, and angular#71884. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Depends on #1. Review only the last commit; the first one is #1.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
After #1, a component whose selector matches
<ng-container>or<ng-template>gets the NG8032warning. The template still fails when it renders: dev mode throws an assertion, and production
mode throws a DOM
HierarchyRequestError.Issue Number: N/A (issue draft not posted yet)
What is the new behavior?
NG8032 is an error. It isn't configurable.
Does this PR introduce a breaking change?
A component whose selector matches
<ng-container>or<ng-template>fails to compile. Such atemplate already failed when it rendered; only a template that never renders the element, such as
one behind an
@ifthat is always false, compiled and ran before.Migration: use an element that matches the component's selector.
Other information