Skip to content

refactor(tree): rework to account for ivy changes - #15503

Merged
mmalerba merged 1 commit into
angular:masterfrom
crisbeto:tree-ivy-refactor
Mar 18, 2019
Merged

refactor(tree): rework to account for ivy changes#15503
mmalerba merged 1 commit into
angular:masterfrom
crisbeto:tree-ivy-refactor

Conversation

@crisbeto

Copy link
Copy Markdown
Member

Reworks the MatTree and CdkTree components to account for some of the changes in Ivy. This includes:

  • Changing the padding directive to account for a different time at which static inputs are initialized.
  • Changing the toggle directive to account for inheritance of host listeners working differently.
  • Switching to Default change detection, because the way embedded views are checked is slightly different.
  • Using descendants: true to find the nested node outlet in order to handle a slight difference in how indirect content children are matched.

@crisbetocrisbeto added the P2 The issue is important to a large percentage of users, with a workaround label Mar 16, 2019
@googlebotgooglebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Mar 16, 2019
Reworks the `MatTree` and `CdkTree` components to account for some of the changes in Ivy. This includes:
* Changing the padding directive to account for a different time at which static inputs are initialized.
* Changing the toggle directive to account for inheritance of host listeners working differently.
* Switching to `Default` change detection, because the way embedded views are checked is slightly different.
* Using `descendants: true` to find the nested node outlet in order to handle a slight difference in how indirect content children are matched.
@mmalerba
mmalerba merged commit 1421184 into angular:masterMar 18, 2019
mmalerba pushed a commit that referenced this pull request Mar 18, 2019
Equivalent of #15503 for the Ivy branch.
Reworks the `MatTree` and `CdkTree` components to account for some of the changes in Ivy. This includes:
* Changing the padding directive to account for a different time at which static inputs are initialized.
* Changing the toggle directive to account for inheritance of host listeners working differently.
* Switching to `Default` change detection, because the way embedded views are checked is slightly different.
* Using `descendants: true` to find the nested node outlet in order to handle a slight difference in how indirect content children are matched.
@mmalerbammalerba added the target: patch This PR is targeted for the next patch release label Mar 18, 2019
mmalerba pushed a commit that referenced this pull request Mar 18, 2019
Reworks the `MatTree` and `CdkTree` components to account for some of the changes in Ivy. This includes:
* Changing the padding directive to account for a different time at which static inputs are initialized.
* Changing the toggle directive to account for inheritance of host listeners working differently.
* Switching to `Default` change detection, because the way embedded views are checked is slightly different.
* Using `descendants: true` to find the nested node outlet in order to handle a slight difference in how indirect content children are matched.
mmalerba pushed a commit that referenced this pull request Mar 18, 2019
Reworks the `MatTree` and `CdkTree` components to account for some of the changes in Ivy. This includes:
* Changing the padding directive to account for a different time at which static inputs are initialized.
* Changing the toggle directive to account for inheritance of host listeners working differently.
* Switching to `Default` change detection, because the way embedded views are checked is slightly different.
* Using `descendants: true` to find the nested node outlet in order to handle a slight difference in how indirect content children are matched.
@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-botangular-automatic-lock-botBot locked and limited conversation to collaborators Sep 10, 2019
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

cla: yesPR author has agreed to Google's Contributor License AgreementP2The issue is important to a large percentage of users, with a workaroundtarget: patchThis PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

@crisbeto@jelbourn@googlebot@mmalerba@andrewseguin