-
Notifications
You must be signed in to change notification settings - Fork 6.8k
fix(material/tree): not rendering initial data from flat data source #22340
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
Conversation
@andrewseguin what is the standard response to people using fake private props? Isn't this discouraged & not supported? |
2693a46
to
94df9fb
Compare
I've made it public again. Usually the underscore prefix means that it's private so it should discourage people from using it, but there's nothing actually stopping them from doing it. |
Yeah...they should not have been using it but unless we put |
@andrewseguin My thoughts exactly. I know literally nothing about the angular material tree, but is there another way to access the |
94df9fb
to
750ee4e
Compare
@crisbeto I think we should be good to land this internally but there are some merge conflicts that need to be resolved before I can run presubmits |
The `MatTreeFlatDataSource` has an `initialData` parameter which doesn't work, because it only assigns the data to one of the three streams used to render the tree. These changes also make some underscored properties private. Fixes angular#22282.
Done. |
750ee4e
to
29f7eee
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. |
The
MatTreeFlatDataSource
has aninitialData
parameter which doesn't work, because it only assigns the data to one of the three streams used to render the tree.These changes also make some underscored properties private.
Fixes #22282.