help(MatTreeFlatDataSource): expandedData / flattenedData properties
See original GitHub issueWhat are you trying to do?
Access expandedData
and flattenedData
from the datasource.
What troubleshooting steps have you tried?
Both are private since https://github.com/angular/components/pull/22340
Reproduction
NA
Environment
- Angular: 12.0.4
- CDK/Material: 12.0.4
- Browser(s): NA
- Operating System (e.g. Windows, macOS, Ubuntu): NA
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
How do I access flattenedData whn using ... - Stack Overflow
It seems that I cannot access the _flattenData property anymore from MatTreeFlatDataSource. This part of code use to work before the upgrade ...
Read more >Tree | Angular Material
Captures the node's template and a when predicate that describes when this node should be used. Selector: [matTreeNodeDef]. Properties. Name, Description. @ ...
Read more >Mat-Tree: Adding a child to an existing node does not ... - GitHub
nestedDataSource.data to a new reference (under the hood it uses a getter to check when the data property is changed to an entirely...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ll mark this as a feature request. It’s worth noting that if a property name starts with an underscore (like with
_expandedData
and_flattenedData
), it means that it’s internal and it can change or be removed without any sort of deprecation period.Thank you for submitting your feature request! Looks like during the polling process it didn’t collect a sufficient number of votes to move to the next stage.
We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular’s scope, we’d encourage you to collaborate with the community on publishing it as an open source package.
You can find more details about the feature request process in our documentation.