-
Notifications
You must be signed in to change notification settings - Fork 18
Use unique keys and avoid duplicated or false nodes #131
Conversation
This reverts commit 9a391e9.
cool! 👍 |
You have seen it working i.e. in sandbox? |
As the get |
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.
all the karma tests are failing localy, can you fix that please
PhantomJS 1.9.8 (Linux 0.0.0) The Fancytree adapter automatically expands nodes when root is one folder FAILED
TypeError: 'null' is not an object (evaluating 'tree.getNodeByKey('cms').isExpanded')
Added In other words: ready to merge imo |
@wouterj you can merge from my POV, but i don't really understand the one failing build, seems as one before you last commit. |
I wil merge and have a look into the next issue. |
@ElectricMaxxx failing build is probably a bug on Travis's side. No problem here for us. |
/fixes #128, symfony-cmf/sonata-phpcr-admin-integration-bundle#73
/replaces #125
Instead of building the path using keys, the path is now saved in a
refPath
data property per node. This fixes the issue with unique keys (#128). It also makes it easier to fix false or duplicated nodes./cc @ElectricMaxxx