-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
feat(tree): merge tree branch to master #9796
Conversation
data source input and template, except that its element and attribute selectors will be prefixed | ||
with `mat-` instead of `cdk-`. | ||
|
||
There are two types of trees: Flat tree and Nested Tree. The DOM structures are different for these |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small nitpick: Flat tree and Nested tree or Flat Tree and Nested Tree
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Caretaker note: will need build rules |
So there's good news and bad news. 👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there. 😕 The bad news is that it appears that one or more commits were authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request. Note to project maintainer: This is a terminal state, meaning the |
Will need #9877 to fix the lint rules |
* Add Cdk Tree component * Put tree control in control folder. Removed NestedNode FlatNode types and add getLevel getChildren isExpandable in TreeControl. * Use static varaible to pass node data * fix lint * another round * update documents according to comments
aff43c0
to
e9a6a63
Compare
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
No description provided.