From 07b4d07e20b2f105cda4030f6c8bbf67e42a9f48 Mon Sep 17 00:00:00 2001 From: Cristhian Garcia Date: Tue, 29 Oct 2024 09:00:22 -0500 Subject: [PATCH] docs: update create next component version docstring --- openedx_learning/apps/authoring/components/api.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/openedx_learning/apps/authoring/components/api.py b/openedx_learning/apps/authoring/components/api.py index 9561bbb6..f58dca6d 100644 --- a/openedx_learning/apps/authoring/components/api.py +++ b/openedx_learning/apps/authoring/components/api.py @@ -141,7 +141,7 @@ def create_next_component_version( A very common pattern for making a new ComponentVersion is going to be "make it just like the last version, except changing these one or two things". Before calling this, you should create any new contents via the contents - API, since ``content_to_replace`` needs Content IDs for the values. + API or send the content bytes as part of ``content_to_replace`` values. The ``content_to_replace`` dict is a mapping of strings representing the local path/key for a file, to ``Content.id`` or content bytes values. Using