From bbce7893c53274b58986ac47bc66aceeab883bf9 Mon Sep 17 00:00:00 2001 From: Maria Grimaldi Date: Tue, 5 Nov 2024 07:22:57 -0400 Subject: [PATCH] docs: Update docs/decisions/0017-generalized-containers.rst --- docs/decisions/0017-generalized-containers.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/decisions/0017-generalized-containers.rst b/docs/decisions/0017-generalized-containers.rst index 8b2f1001..2518c009 100644 --- a/docs/decisions/0017-generalized-containers.rst +++ b/docs/decisions/0017-generalized-containers.rst @@ -47,8 +47,8 @@ Decisions - A new version is created if and only if the container itself changes (e.g., title, ordering of contents, adding or removing content) and not when its content changes (e.g., a component in a Unit is updated with new text). - Changes to the order of members within a container require creating a new version of the container with the new ordering. -- Changes in pinned published or draft states require creating a new version of the container to maintain the state of the content for the previous version. - Each time a new version is created because of metadata changed, its members are copied from the previous version to preserve the state of the content at that time. +- Changes in pinned published or draft states require creating a new version of the container to maintain the state of the content for the previous version. - When using version-agnostic references to members, no new version is created when members change since the latest draft or published state is always used. - If a member is soft-deleted, the container will create a new version with the member removed.