Expand children when pattern matches

[takeit]

Hi,

I have collapsed tree for better performance. Is it possible on search to expand the root node if it contains child whose name matches the search value ?

Best

[jrencz]

Could you please provide a demo on plunker (or any other service of your choice)?

Technically there's nothing that would stop you from keeping your nodes hidden because the filter operates on the data, not on DOM nodes.
I assume you have a piece of logic for enabling/disabling the child nodes. You'd have to incorporate the filter into that logic the same way it is now responsible for hiding (or dimming) the non-matching nodes (see the demo)

[TLenahan]

I also have this same issue. The tree is initially collapsed, and upon searching for a child node, no nodes are expanded. The best example (see plunk ) I have would be to type 'Kev' and nothing will happen. Then type 'Kevv' and as should be, nothing happens. BUT upon removing the extra 'v', the correct functionality ocurrs. I am not too sure why the child nodes are not expanded unless a typo happens and is corrected. I have tried to correct this but I just can't figure it out.

[jrencz]

@TLenahan please compare your example and mine: http://plnkr.co/edit/NNSgfC0Qs8vr9iIZTJp2?p=preview

I added pattern && to collapsed attributes.
This is because attribute observer (which is used internally by the angular-ui-tree to allow toggling nodes using collapsed attribute) needs the value of the expression to change.
treeFilter matches when pattern is an empty string. A value filter returns must change to false and then back to true. This explains why a typo "helps".

[michaelb87]

Cool thanks for the help!
Also I'd like to mention that the subitemlist has to be called 'items'. I had problems using a custom name like 'childs'.

Do you have a solution of triggering the treeFilter if the user clears the input again? It will stay expanded currently. I think this is connected with the filter needing to change state.