a bug found in the Tasks demo.
Some parent resources can contain no children, and in this case they are rendered as a "child" resource.
Steps to reproduce:
1. Go to the Tasks example https://www.bryntum.com/examples/scheduler/tasks/
2. In Chrome console, add a new record to resourceStore with empty "clients" property:
newRecord = {
"id" : 100,
"name" : "TEST",
"title" : "TEST",
"expanded": true,
"clients" : []
}
scheduler.resourceStore.add(newRecord);
3. Add another record which has children metadata:
newRecord = {
"id" : 200,
"name" : "TEST2",
"title" : "TEST2",
"expanded": true,
"clients" : [{"id": 2001, "name": "child of TEST2", "color": "teal"}]
}
scheduler.resourceStore.add(newRecord);
4. Add a new event to the "TEST2" resource
5. Try to collapse/expand the new "TEST2" resource
Actual result: child resources for TEST2 are not shown.
Expected result: child resources are shown after the parent resource is expanded.
6. After "#5" is acknowledged, try to collapse/expand any of the initial parent resources.
Actual result: child resources for TEST2 become visible.
I can share a screencast in case #5-6 are not reproduced by the team.