From a58ee8d67683e26dc2075353d4562bd3e43d9544 Mon Sep 17 00:00:00 2001 From: Gabor Hojtsy Date: Thu, 12 Oct 2017 12:03:55 +0200 Subject: [PATCH] =?UTF-8?q?Issue=20#2892377=20by=20Wim=20Leers,=20G=C3=A1b?= =?UTF-8?q?or=20Hojtsy:=20Document=20relationship=20of=20entities,=20entit?= =?UTF-8?q?y=20revisions=20and=20entity=20translations?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- core/lib/Drupal/Core/Entity/entity.api.php | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/core/lib/Drupal/Core/Entity/entity.api.php b/core/lib/Drupal/Core/Entity/entity.api.php index 5387c7ef7e3..bf4abec5c8c 100644 --- a/core/lib/Drupal/Core/Entity/entity.api.php +++ b/core/lib/Drupal/Core/Entity/entity.api.php @@ -113,6 +113,17 @@ use Drupal\node\Entity\NodeType; * @endcode * This involves the same hooks and operations as regular entity loading. * + * @section entities_revisions_translations Entities, revisions and translations + * + * A translation is not a revision and a revision is not necessarily a + * translation. Revisions and translations are the two axes on the "spreadsheet" + * of an entity. If you use the built-in UI and have revisions enabled, then a + * new translation change would create a new revision (with a copy of all data + * for other languages in that revision). If an entity does not use revisions or + * the entity is being modified via the API, then multiple translations can be + * modified in a single revision. Conceptually, the revisions are columns on the + * spreadsheet and translations are rows. + * * @section save Save operations * To update an existing entity, you will need to load it, change properties, * and then save; as described above, when creating a new entity, you will also