Skip to content

refactor(core): re-use isDetachedByI18n#59668

Closed
arturovt wants to merge 1 commit intoangular:mainfrom
arturovt:refactor/core-reuse-isDetachedByI18n
Closed

refactor(core): re-use isDetachedByI18n#59668
arturovt wants to merge 1 commit intoangular:mainfrom
arturovt:refactor/core-reuse-isDetachedByI18n

Conversation

@arturovt
Copy link
Copy Markdown
Contributor

We already have a function called isDetachedByI18n which checks whether a tNode is in isDetached state; as thus, there's no reason to apply those checks manually.

@pullapprove pullapprove bot requested a review from devversion January 22, 2025 17:35
@angular-robot angular-robot bot added the area: core Issues related to the framework runtime label Jan 22, 2025
@ngbot ngbot bot added this to the Backlog milestone Jan 22, 2025
We already have a function called `isDetachedByI18n` which checks whether a `tNode` is in `isDetached` state; as thus, there's no reason to apply those checks manually.
@arturovt arturovt force-pushed the refactor/core-reuse-isDetachedByI18n branch from cd3d145 to e7c9ac1 Compare January 24, 2025 09:26
@devversion devversion added action: merge The PR is ready for merge by the caretaker target: patch This PR is targeted for the next patch release labels Jan 24, 2025
@pkozlowski-opensource
Copy link
Copy Markdown
Member

This PR was merged into the repository by commit e271639.

The changes were merged into the following branches: main, 19.1.x

pkozlowski-opensource pushed a commit that referenced this pull request Jan 24, 2025
We already have a function called `isDetachedByI18n` which checks whether a `tNode` is in `isDetached` state; as thus, there's no reason to apply those checks manually.

PR Close #59668
@arturovt arturovt deleted the refactor/core-reuse-isDetachedByI18n branch January 24, 2025 21:59
PrajaktaB27 pushed a commit to PrajaktaB27/angular that referenced this pull request Feb 7, 2025
We already have a function called `isDetachedByI18n` which checks whether a `tNode` is in `isDetached` state; as thus, there's no reason to apply those checks manually.

PR Close angular#59668
@angular-automatic-lock-bot
Copy link
Copy Markdown

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 Feb 24, 2025
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.

3 participants