Description:
We should review how version history is displayed in Abzu and how it is stored in Tiamat.
Currently, you cannot view version history for a stop that has become a child stop, even though its version number is incremented each time the parent stop is saved.
Similarly, the parent stop’s version is incremented even when only the child stop changes, but the parent stop’s version history does not indicate which child stop was modified.
Problem Scenarios:
If a stop was previously multimodal but is now mono, the version history becomes largely meaningless.
Changes to child stops are not visible in their own version history after they become children.
Parent stops’ version history is incremented without clear context of which child stop triggered the change.
Steps to reproduce:
Create a multimodal stop with multiple children.
Save the parent stop – version history updates.
Change only a child stop.
Observe that:
The child’s version history is not updated/displayed.
The parent’s version increments, but without showing which child changed.
Expected behavior:
Each stop (parent or child) should maintain its own version history.
Version history should clearly indicate the source of a version change (whether it was a direct change to the stop or due to changes in related stops).
If a stop changes from multimodal to mono, version history should remain meaningful.
Proposed fix:
Update the way Tiamat stores version history to keep parent and child histories independent.
Enhance Abzu’s display logic to show relevant version changes for both parents and children.
Include references in parent version history indicating which child stop was modified.
Description:
We should review how version history is displayed in Abzu and how it is stored in Tiamat.
Currently, you cannot view version history for a stop that has become a child stop, even though its version number is incremented each time the parent stop is saved.
Similarly, the parent stop’s version is incremented even when only the child stop changes, but the parent stop’s version history does not indicate which child stop was modified.
Problem Scenarios:
If a stop was previously multimodal but is now mono, the version history becomes largely meaningless.
Changes to child stops are not visible in their own version history after they become children.
Parent stops’ version history is incremented without clear context of which child stop triggered the change.
Steps to reproduce:
Create a multimodal stop with multiple children.
Save the parent stop – version history updates.
Change only a child stop.
Observe that:
The child’s version history is not updated/displayed.
The parent’s version increments, but without showing which child changed.
Expected behavior:
Each stop (parent or child) should maintain its own version history.
Version history should clearly indicate the source of a version change (whether it was a direct change to the stop or due to changes in related stops).
If a stop changes from multimodal to mono, version history should remain meaningful.
Proposed fix:
Update the way Tiamat stores version history to keep parent and child histories independent.
Enhance Abzu’s display logic to show relevant version changes for both parents and children.
Include references in parent version history indicating which child stop was modified.