Tree: Bad initialization of expanded keys when filter option is present

[RolT]

Describe the bug

The initial value given to expandedKeys gets overridden if a filter field is present, even if the filter value is empty.

In the reproducer, both trees use the same initial expandedKeys but the tree with the filter field is not initialized properly (all nodes are collapsed).

Reproducer

https://stackblitz.com/edit/edubbxcg

System Information

primereact: 10.9.7

Steps to reproduce the behavior

No response

Expected behavior

Both trees should be the same upon first render.

[RolT]

It's not just about initialization, when changing the model all the nodes are collapsed if the filter is empty:

https://stackblitz.com/edit/edubbxcg-bpppr4jy

1. Expand a node
2. Click on 'Add item'
3. All the nodes are collapsed

[domhaas]

Thanks @RolT for posting this - I have the same issue.

[Coderxrohan]

Issue
expandedKeys were being reset when a filter input was present, even if the filter was empty, causing nodes to collapse unexpectedly on init and model updates.

Fix
Filter-related expanded keys are now toggled only when the filter is actually used, preserving the original tree state otherwise.

Impact
Initial render and runtime updates behave correctly; expanded state is no longer lost when the filter is empty.

⭐ Rating: 5/5

[Coderxrohan]

Hi @melloware, this PR addresses the expandedKeys reset when a filter input is present but empty.
Reviewed and tested with the repro — looks good and ready to merge. Thanks!