You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found a rendering issue with situations regarding children of one side of a couple or children of a parent with multiple spouse. In all of the following examples, the rootId is "Mother".
This can be imagined as a story of a divorced couple with a child, where the mother remarries, and the child's father is removed from the family tree.
Here's a similar situation, the one that got me investigating this. This is a single mother of one who (re)marries and has another kid with the new guy:
If it is the code, I have a feeling it has to do with createChildUnitsFunc and/or getSpouseNodesFunc. I haven't been able to dig too far into it, but it seems that the way Units are created pushes out children that aren't the full offspring of the computed parents, and parents who are couples aren't offered to createChildUnits as potential single parents. Or something like that. I'll see if I can do more research, but no promises. This might be related to #12.
The text was updated successfully, but these errors were encountered:
I found a rendering issue with situations regarding children of one side of a couple or children of a parent with multiple spouse. In all of the following examples, the rootId is "Mother".
This can be imagined as a story of a divorced couple with a child, where the mother remarries, and the child's father is removed from the family tree.
Standard unit, renders correctly:
Actual & Expected:
When the mother remarries, the child is now linked only to the father:
Actual:
Expected:
If the father is removed, the child disappears:
Actual:
Expected:
When the 2nd husband is removed, the child reappears:
Actual & Expected:
Here's a similar situation, the one that got me investigating this. This is a single mother of one who (re)marries and has another kid with the new guy:
Actual:
Expected:
Are my expectations off, or is the code?
If it is the code, I have a feeling it has to do with
createChildUnitsFunc
and/orgetSpouseNodesFunc
. I haven't been able to dig too far into it, but it seems that the way Units are created pushes out children that aren't the full offspring of the computed parents, and parents who are couples aren't offered to createChildUnits as potential single parents. Or something like that. I'll see if I can do more research, but no promises. This might be related to #12.The text was updated successfully, but these errors were encountered: