[END-7969] Fixed children/parent relationships in admin templates #11156
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
Admin templates used nonexistent fields to display children and parent of a node (potentially new fields were added but the old fields weren't replaced by new ones). The templates used
parent
andchildren
fields. However an endpoint that adds children and parent to a node uses fieldsdescendants
(or throughNodeRelation
usingget_nodes
method) andparent_node
property through_parents
fieldChanges
Use correct fields
Notes
Deletion of children nodes that are displayed now is broken. Together with Mark decided to create a separate ticket for this issue
Ticket
https://openscience.atlassian.net/browse/ENG-7969?atlOrigin=eyJpIjoiMGNhZWZhMWM4ZmM2NGNlM2E4ZDQ0OTg1ZjgyZmI1NGEiLCJwIjoiaiJ9