Skip to content

Conversation

AndrewKushnir
Copy link
Contributor

Prior to this commit, there were no advance instructions generated before i18nExp instructions and as a result, lifecycle hooks for components used inside i18n blocks were flushed too late. This commit adds the logic to generate advance instructions in front of i18nExp ones (similar to what we have in other places like interpolations, property bindings, etc), so that the necessary lifecycle hooks are flushed before expression value is captured.

This PR resolves FW-1775.

PR Type

What kind of change does this PR introduce?

  • Bugfix

Does this PR introduce a breaking change?

  • Yes
  • No

@AndrewKushnir AndrewKushnir added type: bug/fix state: WIP area: i18n Issues related to localization and internationalization target: patch This PR is targeted for the next patch release comp: ivy labels Dec 16, 2019
@ngbot ngbot bot modified the milestone: needsTriage Dec 16, 2019
@AndrewKushnir AndrewKushnir force-pushed the FW-1775_advance_in_i18n branch from 94da2af to 1792f5a Compare December 17, 2019 00:16
@AndrewKushnir
Copy link
Contributor Author

AndrewKushnir commented Dec 17, 2019

Presubmit

@AndrewKushnir AndrewKushnir added action: review The PR is still awaiting reviews from at least one requested reviewer and removed state: WIP labels Dec 17, 2019
@AndrewKushnir AndrewKushnir marked this pull request as ready for review December 17, 2019 19:52
@AndrewKushnir AndrewKushnir requested review from a team as code owners December 17, 2019 19:52
Copy link
Member

@crisbeto crisbeto left a comment

Choose a reason for hiding this comment

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

A couple of nits, but otherwise LGTM 👍 .

Prior to this commit, there were no `advance` instructions generated before `i18nExp` instructions and as a result, lifecycle hooks for components used inside i18n blocks were flushed too late. This commit adds the logic to generate `advance` instructions in front of `i18nExp` ones (similar to what we have in other places like interpolations, property bindings, etc), so that the necessary lifecycle hooks are flushed before expression value is captured.
@AndrewKushnir AndrewKushnir force-pushed the FW-1775_advance_in_i18n branch from 8a4f645 to edbde2a Compare January 3, 2020 23:59
Copy link
Contributor

@kara kara left a comment

Choose a reason for hiding this comment

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

LGTM

@kara kara added action: merge The PR is ready for merge by the caretaker action: presubmit The PR is in need of a google3 presubmit and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Jan 7, 2020
@AndrewKushnir
Copy link
Contributor Author

Presubmit

@AndrewKushnir AndrewKushnir removed the action: presubmit The PR is in need of a google3 presubmit label Jan 7, 2020
alxhub pushed a commit that referenced this pull request Jan 7, 2020
Prior to this commit, there were no `advance` instructions generated before `i18nExp` instructions and as a result, lifecycle hooks for components used inside i18n blocks were flushed too late. This commit adds the logic to generate `advance` instructions in front of `i18nExp` ones (similar to what we have in other places like interpolations, property bindings, etc), so that the necessary lifecycle hooks are flushed before expression value is captured.

PR Close #34436
@alxhub alxhub closed this in b4c5bdb Jan 7, 2020
@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 Feb 7, 2020
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: i18n Issues related to localization and internationalization cla: yes target: patch This PR is targeted for the next patch release type: bug/fix
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants