Skip to content

refactor(core): disable renderer3 unless explicitly enabled by tests#46530

Closed
alxhub wants to merge 1 commit intoangular:mainfrom
alxhub:fixit-block-renderer3
Closed

refactor(core): disable renderer3 unless explicitly enabled by tests#46530
alxhub wants to merge 1 commit intoangular:mainfrom
alxhub:fixit-block-renderer3

Conversation

@alxhub
Copy link
Member

@alxhub alxhub commented Jun 27, 2022

The Renderer3 abstraction in Angular was an experimental code path in Ivy
which uses direct DOM operations instead of the former Renderer2 path. To
allow Renderer2 to tree-shake away, Renderer3 is the default unless
Renderer2 is provided. It was only an experiment, and never meant to be a
production code path.

However, it's possible for Renderer3 to leak into user code. This commit
prevents that possibility by causing the Renderer3 path to throw, unless
an explicit function has been called to enable it.

The `Renderer3` abstraction in Angular was an experimental code path in Ivy
which uses direct DOM operations instead of the former `Renderer2` path. To
allow `Renderer2` to tree-shake away, `Renderer3` is the default _unless_
`Renderer2` is provided. It was only an experiment, and never meant to be a
production code path.

However, it's possible for `Renderer3` to leak into user code. This commit
prevents that possibility by causing the `Renderer3` path to throw, unless
an explicit function has been called to enable it.
@alxhub alxhub force-pushed the fixit-block-renderer3 branch from 38816f4 to 5040d2a Compare June 27, 2022 22:46
@AndrewKushnir AndrewKushnir added this to the Fixit H1'2022 milestone Jun 28, 2022
@ngbot ngbot bot removed this from the Fixit H1'2022 milestone Jun 28, 2022
@dylhunn dylhunn added the area: core Issues related to the framework runtime label Jun 28, 2022
@ngbot ngbot bot added this to the Backlog milestone Jun 28, 2022
@alxhub
Copy link
Member Author

alxhub commented Jun 28, 2022

TGP

@alxhub alxhub added action: merge The PR is ready for merge by the caretaker target: patch This PR is targeted for the next patch release labels Jun 28, 2022
@alxhub alxhub modified the milestones: Backlog, Fixit H1'2022 Jun 28, 2022
Copy link
Member

@pkozlowski-opensource pkozlowski-opensource left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

@AndrewKushnir AndrewKushnir left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@dylhunn
Copy link
Contributor

dylhunn commented Jun 28, 2022

This PR was merged into the repository by commit a322b7d.

@dylhunn dylhunn closed this in a322b7d Jun 28, 2022
dylhunn pushed a commit that referenced this pull request Jun 28, 2022
…46530)

The `Renderer3` abstraction in Angular was an experimental code path in Ivy
which uses direct DOM operations instead of the former `Renderer2` path. To
allow `Renderer2` to tree-shake away, `Renderer3` is the default _unless_
`Renderer2` is provided. It was only an experiment, and never meant to be a
production code path.

However, it's possible for `Renderer3` to leak into user code. This commit
prevents that possibility by causing the `Renderer3` path to throw, unless
an explicit function has been called to enable it.

PR Close #46530
@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jul 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker area: core Issues related to the framework runtime target: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants