fix(compiler): Fix the template pipeline option

[dylhunn]

The useTemplatePipeline option was not properly threaded through the component handler.

[alfaproject]

Is there any documentation you can share about this feature or maybe a small summary with pros/cons and what the future holds? I'm open to give this feature a try in our projects to give early feedback if any but I'm curious to what I should be looking at

[dylhunn]

@alfaproject

The Template Pipeline is a brand new backend for the Angular compiler, replacing TemplateDefinitionBuilder and friends. It generates the Ivy instructions corresponding to an input template (or host binding). The Template Pipeline has an all-new design based on an intermediate representation compiled over many phases, which will allow us to experiment with compiler changes more easily in the future.

Users should experience no changes, since Template Pipeline produces almost-identical code to TemplateDefinitionBuilder. You can think of it as an internal-only change, which will hopefully allow us to build features such as Signal-based components faster.

We are adding this option for our own testing purposes, to ensure that there are no behavior changes in applications.

[alfaproject]

@dylhunn I see, thank you for your reply!

[dylhunn]

caretaker: no g3 impact, and hand-tested when enabled

[jessicajaniuk]

This PR was merged into the repository by commit 7b4d275.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}