Skip to content

fix(tree): allow use of FlatTreeControl's trackBy function in MatTreeFlatDataSource and MatTreeFlattener #19600

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 29, 2020

Conversation

tjaneczko
Copy link
Contributor

The ability to track tree-node expansion via a trackBy function was added to FlatTreeControl in #18708. It's currently not feasible to use this in combination with MatTreeFlattener or MatTreeFlatDataSource, as they don't support the additional type variable in FlatTreeControl. This PR adds the additional type variable to these classes in a similar manner to how they were added to FlatTreeControl.

@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jun 10, 2020
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.

LGTM

@crisbeto crisbeto added merge: fix commit message When the PR is merged, rewrites/fixups of the commit messages are needed lgtm action: merge The PR is ready for merge by the caretaker P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release labels Jun 13, 2020
@crisbeto
Copy link
Member

Commit message fixup: should start with fix(tree):.

@tjaneczko tjaneczko changed the title Allow use of FlatTreeControl's trackBy function in MatTreeFlatDataSource and MatTreeFlattener fix(tree): allow use of FlatTreeControl's trackBy function in MatTreeFlatDataSource and MatTreeFlattener Jun 15, 2020
@tjaneczko
Copy link
Contributor Author

Thanks for the review! I updated the title, do I also need to update the messages for individual commits within this PR? Do I need to merge these commits together?

@crisbeto
Copy link
Member

I think it should be fine since the caretaker squashes the commits when they merge something in.

@jelbourn jelbourn added G This is is related to a Google internal issue target: minor This PR is targeted for the next minor release and removed target: patch This PR is targeted for the next patch release labels Jun 24, 2020
@jelbourn jelbourn merged commit 8ea3558 into angular:master Jun 29, 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 Aug 16, 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 cla: yes PR author has agreed to Google's Contributor License Agreement G This is is related to a Google internal issue merge: fix commit message When the PR is merged, rewrites/fixups of the commit messages are needed P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: minor This PR is targeted for the next minor release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants