entity.api.php 77.8 KB
Newer Older
1 2 3 4
<?php

/**
 * @file
5
 * Hooks and documentation related to entities.
6 7
 */

8
use Drupal\Core\Access\AccessResult;
9
use Drupal\Core\Entity\ContentEntityInterface;
10
use Drupal\Core\Entity\DynamicallyFieldableEntityStorageInterface;
11
use Drupal\Core\Field\BaseFieldDefinition;
12
use Drupal\Core\Render\Element;
13
use Drupal\language\Entity\ContentLanguageSettings;
14
use Drupal\node\Entity\NodeType;
15

16 17 18 19 20 21 22 23 24
/**
 * @defgroup entity_crud Entity CRUD, editing, and view hooks
 * @{
 * Hooks used in various entity operations.
 *
 * Entity create, read, update, and delete (CRUD) operations are performed by
 * entity storage classes; see the
 * @link entity_api Entity API topic @endlink for more information. Most
 * entities use or extend the default classes:
25
 * \Drupal\Core\Entity\Sql\SqlContentEntityStorage for content entities, and
26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115
 * \Drupal\Core\Config\Entity\ConfigEntityStorage for configuration entities.
 * For these entities, there is a set of hooks that is invoked for each
 * CRUD operation, which module developers can implement to affect these
 * operations; these hooks are actually invoked from methods on
 * \Drupal\Core\Entity\EntityStorageBase.
 *
 * For content entities, viewing and rendering are handled by a view builder
 * class; see the @link entity_api Entity API topic @endlink for more
 * information. Most view builders extend or use the default class
 * \Drupal\Core\Entity\EntityViewBuilder.
 *
 * Entity editing (including adding new entities) is handled by entity form
 * classes; see the @link entity_api Entity API topic @endlink for more
 * information. Most entity editing forms extend base classes
 * \Drupal\Core\Entity\EntityForm or \Drupal\Core\Entity\ContentEntityForm.
 * Note that many other operations, such as confirming deletion of entities,
 * also use entity form classes.
 *
 * This topic lists all of the entity CRUD and view operations, and the hooks
 * and other operations that are invoked (in order) for each operation. Some
 * notes:
 * - Whenever an entity hook is invoked, there is both a type-specific entity
 *   hook, and a generic entity hook. For instance, during a create operation on
 *   a node, first hook_node_create() and then hook_entity_create() would be
 *   invoked.
 * - The entity-type-specific hooks are represented in the list below as
 *   hook_ENTITY_TYPE_... (hook_ENTITY_TYPE_create() in this example). To
 *   implement one of these hooks for an entity whose machine name is "foo",
 *   define a function called mymodule_foo_create(), for instance. Also note
 *   that the entity or array of entities that are passed into a specific-type
 *   hook are of the specific entity class, not the generic Entity class, so in
 *   your implementation, you can make the $entity argument something like $node
 *   and give it a specific type hint (which should normally be to the specific
 *   interface, such as \Drupal\Node\NodeInterface for nodes).
 * - $storage in the code examples is assumed to be an entity storage
 *   class. See the @link entity_api Entity API topic @endlink for
 *   information on how to instantiate the correct storage class for an
 *   entity type.
 * - $view_builder in the code examples is assumed to be an entity view builder
 *   class. See the @link entity_api Entity API topic @endlink for
 *   information on how to instantiate the correct view builder class for
 *   an entity type.
 * - During many operations, static methods are called on the entity class,
 *   which implements \Drupal\Entity\EntityInterface.
 *
 * @section create Create operations
 * To create an entity:
 * @code
 * $entity = $storage->create();
 *
 * // Add code here to set properties on the entity.
 *
 * // Until you call save(), the entity is just in memory.
 * $entity->save();
 * @endcode
 * There is also a shortcut method on entity classes, which creates an entity
 * with an array of provided property values: \Drupal\Core\Entity::create().
 *
 * Hooks invoked during the create operation:
 * - hook_ENTITY_TYPE_create()
 * - hook_entity_create()
 *
 * See @ref save below for the save portion of the operation.
 *
 * @section load Read/Load operations
 * To load (read) a single entity:
 * @code
 * $entity = $storage->load($id);
 * @endcode
 * To load multiple entities:
 * @code
 * $entities = $storage->loadMultiple($ids);
 * @endcode
 * Since load() calls loadMultiple(), these are really the same operation.
 * Here is the order of hooks and other operations that take place during
 * entity loading:
 * - Entity is loaded from storage.
 * - postLoad() is called on the entity class, passing in all of the loaded
 *   entities.
 * - hook_entity_load()
 * - hook_ENTITY_TYPE_load()
 *
 * When an entity is loaded, normally the default entity revision is loaded.
 * It is also possible to load a different revision, for entities that support
 * revisions, with this code:
 * @code
 * $entity = $storage->loadRevision($revision_id);
 * @endcode
 * This involves the same hooks and operations as regular entity loading.
 *
116 117 118 119 120 121 122 123 124 125 126
 * @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.
 *
127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148
 * @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
 * need to save it. Here is the order of hooks and other events that happen
 * during an entity save:
 * - preSave() is called on the entity object, and field objects.
 * - hook_ENTITY_TYPE_presave()
 * - hook_entity_presave()
 * - Entity is saved to storage.
 * - For updates on content entities, if there is a translation added that
 *   was not previously present:
 *   - hook_ENTITY_TYPE_translation_insert()
 *   - hook_entity_translation_insert()
 * - For updates on content entities, if there was a translation removed:
 *   - hook_ENTITY_TYPE_translation_delete()
 *   - hook_entity_translation_delete()
 * - postSave() is called on the entity object.
 * - hook_ENTITY_TYPE_insert() (new) or hook_ENTITY_TYPE_update() (update)
 * - hook_entity_insert() (new) or hook_entity_update() (update)
 *
 * Some specific entity types invoke hooks during preSave() or postSave()
 * operations. Examples:
149
 * - Field configuration preSave(): hook_field_storage_config_update_forbid()
150 151
 * - Node postSave(): hook_node_access_records() and
 *   hook_node_access_records_alter()
152 153
 * - Config entities that are acting as entity bundles in postSave():
 *   hook_entity_bundle_create()
154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196
 * - Comment: hook_comment_publish() and hook_comment_unpublish() as
 *   appropriate.
 *
 * @section edit Editing operations
 * When an entity's add/edit form is used to add or edit an entity, there
 * are several hooks that are invoked:
 * - hook_entity_prepare_form()
 * - hook_ENTITY_TYPE_prepare_form()
 * - hook_entity_form_display_alter() (for content entities only)
 *
 * @section delete Delete operations
 * To delete one or more entities, load them and then delete them:
 * @code
 * $entities = $storage->loadMultiple($ids);
 * $storage->delete($entities);
 * @endcode
 *
 * During the delete operation, the following hooks and other events happen:
 * - preDelete() is called on the entity class.
 * - hook_ENTITY_TYPE_predelete()
 * - hook_entity_predelete()
 * - Entity and field information is removed from storage.
 * - postDelete() is called on the entity class.
 * - hook_ENTITY_TYPE_delete()
 * - hook_entity_delete()
 *
 * Some specific entity types invoke hooks during the delete process. Examples:
 * - Entity bundle postDelete(): hook_entity_bundle_delete()
 *
 * Individual revisions of an entity can also be deleted:
 * @code
 * $storage->deleteRevision($revision_id);
 * @endcode
 * This operation invokes the following operations and hooks:
 * - Revision is loaded (see @ref load above).
 * - Revision and field information is removed from the database.
 * - hook_ENTITY_TYPE_revision_delete()
 * - hook_entity_revision_delete()
 *
 * @section view View/render operations
 * To make a render array for a loaded entity:
 * @code
 * // You can omit the language ID if the default language is being used.
197
 * $build = $view_builder->view($entity, 'view_mode_name', $language->getId());
198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247
 * @endcode
 * You can also use the viewMultiple() method to view multiple entities.
 *
 * Hooks invoked during the operation of building a render array:
 * - hook_entity_view_mode_alter()
 * - hook_ENTITY_TYPE_build_defaults_alter()
 * - hook_entity_build_defaults_alter()
 *
 * View builders for some types override these hooks, notably:
 * - The Tour view builder does not invoke any hooks.
 * - The Block view builder invokes hook_block_view_alter() and
 *   hook_block_view_BASE_BLOCK_ID_alter(). Note that in other view builders,
 *   the view alter hooks are run later in the process.
 *
 * During the rendering operation, the default entity viewer runs the following
 * hooks and operations in the pre-render step:
 * - hook_entity_view_display_alter()
 * - hook_entity_prepare_view()
 * - Entity fields are loaded, and render arrays are built for them using
 *   their formatters.
 * - hook_entity_display_build_alter()
 * - hook_ENTITY_TYPE_view()
 * - hook_entity_view()
 * - hook_ENTITY_TYPE_view_alter()
 * - hook_entity_view_alter()
 *
 * Some specific builders have specific hooks:
 * - The Node view builder invokes hook_node_links_alter().
 * - The Comment view builder invokes hook_comment_links_alter().
 *
 * After this point in rendering, the theme system takes over. See the
 * @link theme_render Theme system and render API topic @endlink for more
 * information.
 *
 * @section misc Other entity hooks
 * Some types of entities invoke hooks for specific operations:
 * - Searching nodes:
 *   - hook_ranking()
 *   - Query is executed to find matching nodes
 *   - Resulting node is loaded
 *   - Node render array is built
 *   - comment_node_update_index() is called (this adds "N comments" text)
 *   - hook_node_search_result()
 * - Search indexing nodes:
 *   - Node is loaded
 *   - Node render array is built
 *   - hook_node_update_index()
 * @}
 */

248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267
/**
 * @defgroup entity_api Entity API
 * @{
 * Describes how to define and manipulate content and configuration entities.
 *
 * Entities, in Drupal, are objects that are used for persistent storage of
 * content and configuration information. See the
 * @link info_types Information types topic @endlink for an overview of the
 * different types of information, and the
 * @link config_api Configuration API topic @endlink for more about the
 * configuration API.
 *
 * Each entity is an instance of a particular "entity type". Some content entity
 * types have sub-types, which are known as "bundles", while for other entity
 * types, there is only a single bundle. For example, the Node content entity
 * type, which is used for the main content pages in Drupal, has bundles that
 * are known as "content types", while the User content type, which is used for
 * user accounts, has only one bundle.
 *
 * The sections below have more information about entities and the Entity API;
268 269
 * for more detailed information, see
 * https://www.drupal.org/developing/api/entity.
270 271 272 273 274 275 276 277
 *
 * @section define Defining an entity type
 * Entity types are defined by modules, using Drupal's Plugin API (see the
 * @link plugin_api Plugin API topic @endlink for more information about plugins
 * in general). Here are the steps to follow to define a new entity type:
 * - Choose a unique machine name, or ID, for your entity type. This normally
 *   starts with (or is the same as) your module's machine name. It should be
 *   as short as possible, and may not exceed 32 characters.
278 279
 * - Define an interface for your entity's get/set methods, usually extending
 *   either \Drupal\Core\Config\Entity\ConfigEntityInterface or
280 281 282 283 284
 *   \Drupal\Core\Entity\ContentEntityInterface.
 * - Define a class for your entity, implementing your interface and extending
 *   either \Drupal\Core\Config\Entity\ConfigEntityBase or
 *   \Drupal\Core\Entity\ContentEntityBase, with annotation for
 *   \@ConfigEntityType or \@ContentEntityType in its documentation block.
285 286 287 288 289
 *   If you are defining a content entity type, it is recommended to extend the
 *   \Drupal\Core\Entity\EditorialContentEntityBase base class in order to get
 *   out-of-the-box support for Entity API's revisioning and publishing
 *   features, which will allow your entity type to be used with Drupal's
 *   editorial workflow provided by the Content Moderation module.
290 291 292 293 294
 * - The 'id' annotation gives the entity type ID, and the 'label' annotation
 *   gives the human-readable name of the entity type. If you are defining a
 *   content entity type that uses bundles, the 'bundle_label' annotation gives
 *   the human-readable name to use for a bundle of this entity type (for
 *   example, "Content type" for the Node entity).
295 296
 * - The annotation will refer to several handler classes, which you will also
 *   need to define:
297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315
 *   - list_builder: Define a class that extends
 *     \Drupal\Core\Config\Entity\ConfigEntityListBuilder (for configuration
 *     entities) or \Drupal\Core\Entity\EntityListBuilder (for content
 *     entities), to provide an administrative overview for your entities.
 *   - add and edit forms, or default form: Define a class (or two) that
 *     extend(s) \Drupal\Core\Entity\EntityForm to provide add and edit forms
 *     for your entities. For content entities, base class
 *     \Drupal\Core\Entity\ContentEntityForm is a better starting point.
 *   - delete form: Define a class that extends
 *     \Drupal\Core\Entity\EntityConfirmFormBase to provide a delete
 *     confirmation form for your entities.
 *   - view_builder: For content entities and config entities that need to be
 *     viewed, define a class that implements
 *     \Drupal\Core\Entity\EntityViewBuilderInterface (usually extending
 *     \Drupal\Core\Entity\EntityViewBuilder), to display a single entity.
 *   - translation: For translatable content entities (if the 'translatable'
 *     annotation has value TRUE), define a class that extends
 *     \Drupal\content_translation\ContentTranslationHandler, to translate
 *     the content. Configuration translation is handled automatically by the
316
 *     Configuration Translation module, without the need of a handler class.
317
 *   - access: If your configuration entity has complex permissions, you might
318 319
 *     need an access control handling, implementing
 *     \Drupal\Core\Entity\EntityAccessControlHandlerInterface, but most entities
320
 *     can just use the 'admin_permission' annotation instead. Note that if you
321
 *     are creating your own access control handler, you should override the
322 323 324
 *     checkAccess() and checkCreateAccess() methods, not access().
 *   - storage: A class implementing
 *     \Drupal\Core\Entity\EntityStorageInterface. If not specified, content
325
 *     entities will use \Drupal\Core\Entity\Sql\SqlContentEntityStorage, and
326 327
 *     config entities will use \Drupal\Core\Config\Entity\ConfigEntityStorage.
 *     You can extend one of these classes to provide custom behavior.
328
 *   - views_data: A class implementing \Drupal\views\EntityViewsDataInterface
329 330
 *     to provide views data for the entity type. You can autogenerate most of
 *     the views data by extending \Drupal\views\EntityViewsData.
331 332 333
 * - For content entities, the annotation will refer to a number of database
 *   tables and their fields. These annotation properties, such as 'base_table',
 *   'data_table', 'entity_keys', etc., are documented on
334
 *   \Drupal\Core\Entity\EntityType.
335 336 337 338 339
 * - For content entities that are displayed on their own pages, the annotation
 *   will refer to a 'uri_callback' function, which takes an object of the
 *   entity interface you have defined as its parameter, and returns routing
 *   information for the entity page; see node_uri() for an example. You will
 *   also need to add a corresponding route to your module's routing.yml file;
340
 *   see the entity.node.canonical route in node.routing.yml for an example, and see
341
 *   @ref sec_routes below for some notes.
342 343 344
 * - Optionally, instead of defining routes, routes can be auto generated by
 *   providing a route handler. See @ref sec_routes. Otherwise, define routes
 *   and links for the various URLs associated with the entity.
345
 *   These go into the 'links' annotation, with the link type as the key, and
346 347 348 349
 *   the path of this link template as the value. The corresponding route
 *   requires the following route name:
 *   "entity.$entity_type_id.$link_template_type". See @ref sec_routes below for
 *   some routing notes. Typical link types are:
350 351 352 353 354
 *   - canonical: Default link, either to view (if entities are viewed on their
 *     own pages) or edit the entity.
 *   - delete-form: Confirmation form to delete the entity.
 *   - edit-form: Editing form.
 *   - Other link types specific to your entity type can also be defined.
355 356 357 358 359
 * - If your content entity is fieldable, provide 'field_ui_base_route'
 *   annotation, giving the name of the route that the Manage Fields, Manage
 *   Display, and Manage Form Display pages from the Field UI module will be
 *   attached to. This is usually the bundle settings edit page, or an entity
 *   type settings page if there are no bundles.
360 361 362 363 364 365 366 367 368 369
 * - If your content entity has bundles, you will also need to define a second
 *   plugin to handle the bundles. This plugin is itself a configuration entity
 *   type, so follow the steps here to define it. The machine name ('id'
 *   annotation) of this configuration entity class goes into the
 *   'bundle_entity_type' annotation on the entity type class. For example, for
 *   the Node entity, the bundle class is \Drupal\node\Entity\NodeType, whose
 *   machine name is 'node_type'. This is the annotation value for
 *   'bundle_entity_type' on the \Drupal\node\Entity\Node class. Also, the
 *   bundle config entity type annotation must have a 'bundle_of' entry,
 *   giving the machine name of the entity type it is acting as a bundle for.
370
 *   These machine names are considered permanent, they may not be renamed.
371 372 373 374 375 376
 * - Additional annotations can be seen on entity class examples such as
 *   \Drupal\node\Entity\Node (content) and \Drupal\user\Entity\Role
 *   (configuration). These annotations are documented on
 *   \Drupal\Core\Entity\EntityType.
 *
 * @section sec_routes Entity routes
377 378 379 380 381 382 383 384 385 386 387 388
 * Entity routes can be defined in *.routing.yml files, like any other route:
 * see the @link routing Routing API @endlink topic for more information.
 * Another option for entity routes is to use a route provider class, and
 * reference it in the annotations on the entity class: see the end of this
 * section for an example.
 *
 * It's possible to use both a YAML file and a provider class for entity
 * routes, at the same time. Avoid duplicating route names between the two:
 * if a duplicate route name is found in both locations, the one in the YAML
 * file takes precedence; regardless, such duplication can be confusing.
 *
 * Here's an example YAML route specification, for the block configure form:
389
 * @code
390
 * entity.block.edit_form:
391 392 393 394 395 396 397
 *   path: '/admin/structure/block/manage/{block}'
 *   defaults:
 *     _entity_form: 'block.default'
 *     _title: 'Configure block'
 *   requirements:
 *     _entity_access: 'block.update'
 * @endcode
398
 * Some notes on this example:
399 400 401 402 403 404
 * - path: The {block} in the path is a placeholder, which (for an entity) must
 *   always take the form of {machine_name_of_entity_type}. In the URL, the
 *   placeholder value will be the ID of an entity item. When the route is used,
 *   the entity system will load the corresponding entity item and pass it in as
 *   an object to the controller for the route.
 * - defaults: For entity form routes, use _entity_form rather than the generic
405
 *   _controller or _form. The value is composed of the entity type machine name
406 407 408 409
 *   and a form handler type from the entity annotation (see @ref define above
 *   more more on handlers and annotation). So, in this example, block.default
 *   refers to the 'default' form handler on the block entity type, whose
 *   annotation contains:
410
 *   @code
411
 *   handlers = {
412 413 414
 *     "form" = {
 *       "default" = "Drupal\block\BlockForm",
 *   @endcode
415 416 417 418
 * If instead of YAML you want to use a route provider class:
 * - \Drupal\Core\Entity\Routing\DefaultHtmlRouteProvider provides canonical,
 *   edit-form, and delete-form routes.
 * - \Drupal\Core\Entity\Routing\AdminHtmlRouteProvider provides the same
419
 *   routes, set up to use the administrative theme for edit and delete pages.
420 421 422 423 424 425 426 427 428 429
 * - You can also create your own class, extending one of these two classes if
 *   you only want to modify their behaviour slightly.
 *
 * To register any route provider class, add lines like the following to your
 * entity class annotation:
 * @code
 * handlers = {
 *   "route_provider" = {
 *     "html" = "Drupal\Core\Entity\Routing\DefaultHtmlRouteProvider",
 * @endcode
430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470
 *
 * @section bundle Defining a content entity bundle
 * For entity types that use bundles, such as Node (bundles are content types)
 * and Taxonomy (bundles are vocabularies), modules and install profiles can
 * define bundles by supplying default configuration in their config/install
 * directories. (See the @link config_api Configuration API topic @endlink for
 * general information about configuration.)
 *
 * There are several good examples of this in Drupal Core:
 * - The Forum module defines a content type in node.type.forum.yml and a
 *   vocabulary in taxonomy.vocabulary.forums.yml
 * - The Book module defines a content type in node.type.book.yml
 * - The Standard install profile defines Page and Article content types in
 *   node.type.page.yml and node.type.article.yml, a Tags vocabulary in
 *   taxonomy.vocabulary.tags.yml, and a Node comment type in
 *   comment.type.comment.yml. This profile's configuration is especially
 *   instructive, because it also adds several fields to the Article type, and
 *   it sets up view and form display modes for the node types.
 *
 * @section load_query Loading, querying, and rendering entities
 * To load entities, use the entity storage manager, which is an object
 * implementing \Drupal\Core\Entity\EntityStorageInterface that you can
 * retrieve with:
 * @code
 * $storage = \Drupal::entityManager()->getStorage('your_entity_type');
 * // Or if you have a $container variable:
 * $storage = $container->get('entity.manager')->getStorage('your_entity_type');
 * @endcode
 * Here, 'your_entity_type' is the machine name of your entity type ('id'
 * annotation on the entity class), and note that you should use dependency
 * injection to retrieve this object if possible. See the
 * @link container Services and Dependency Injection topic @endlink for more
 * about how to properly retrieve services.
 *
 * To query to find entities to load, use an entity query, which is a object
 * implementing \Drupal\Core\Entity\Query\QueryInterface that you can retrieve
 * with:
 * @code
 * // Simple query:
 * $query = \Drupal::entityQuery('your_entity_type');
 * // Or, if you have a $container variable:
471 472
 * $storage = $container->get('entity_type.manager')->getStorage('your_entity_type');
 * $query = $storage->getQuery();
473
 * @endcode
474
 * If you need aggregation, there is an aggregate query available, which
475 476 477 478
 * implements \Drupal\Core\Entity\Query\QueryAggregateInterface:
 * @code
 * $query \Drupal::entityQueryAggregate('your_entity_type');
 * // Or:
479
 * $query = $storage->getAggregateQuery('your_entity_type');
480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508
 * @endcode
 *
 * In either case, you can then add conditions to your query, using methods
 * like condition(), exists(), etc. on $query; add sorting, pager, and range
 * if needed, and execute the query to return a list of entity IDs that match
 * the query.
 *
 * Here is an example, using the core File entity:
 * @code
 * $fids = Drupal::entityQuery('file')
 *   ->condition('status', FILE_STATUS_PERMANENT, '<>')
 *   ->condition('changed', REQUEST_TIME - $age, '<')
 *   ->range(0, 100)
 *   ->execute();
 * $files = $storage->loadMultiple($fids);
 * @endcode
 *
 * The normal way of viewing entities is by using a route, as described in the
 * sections above. If for some reason you need to render an entity in code in a
 * particular view mode, you can use an entity view builder, which is an object
 * implementing \Drupal\Core\Entity\EntityViewBuilderInterface that you can
 * retrieve with:
 * @code
 * $view_builder = \Drupal::entityManager()->getViewBuilder('your_entity_type');
 * // Or if you have a $container variable:
 * $view_builder = $container->get('entity.manager')->getViewBuilder('your_entity_type');
 * @endcode
 * Then, to build and render the entity:
 * @code
509 510 511
 * // You can omit the language ID, by default the current content language will
 * // be used. If no translation is available for the current language, fallback
 * // rules will be used.
512
 * $build = $view_builder->view($entity, 'view_mode_name', $language->getId());
513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529
 * // $build is a render array.
 * $rendered = drupal_render($build);
 * @endcode
 *
 * @section sec_access Access checking on entities
 * Entity types define their access permission scheme in their annotation.
 * Access permissions can be quite complex, so you should not assume any
 * particular permission scheme. Instead, once you have an entity object
 * loaded, you can check for permission for a particular operation (such as
 * 'view') at the entity or field level by calling:
 * @code
 * $entity->access($operation);
 * $entity->nameOfField->access($operation);
 * @endcode
 * The interface related to access checking in entities and fields is
 * \Drupal\Core\Access\AccessibleInterface.
 *
530
 * The default entity access control handler invokes two hooks while checking
531 532 533 534 535 536 537 538 539 540 541 542 543 544
 * access on a single entity: hook_entity_access() is invoked first, and
 * then hook_ENTITY_TYPE_access() (where ENTITY_TYPE is the machine name
 * of the entity type). If no module returns a TRUE or FALSE value from
 * either of these hooks, then the entity's default access checking takes
 * place. For create operations (creating a new entity), the hooks that
 * are invoked are hook_entity_create_access() and
 * hook_ENTITY_TYPE_create_access() instead.
 *
 * The Node entity type has a complex system for determining access, which
 * developers can interact with. This is described in the
 * @link node_access Node access topic. @endlink
 *
 * @see i18n
 * @see entity_crud
545
 * @see \Drupal\Core\Entity\EntityManagerInterface::getTranslationFromContext()
546 547 548
 * @}
 */

549 550 551 552 553
/**
 * @addtogroup hooks
 * @{
 */

554 555 556 557 558 559 560 561
/**
 * Control entity operation access.
 *
 * @param \Drupal\Core\Entity\EntityInterface $entity
 *   The entity to check access to.
 * @param string $operation
 *   The operation that is to be performed on $entity.
 * @param \Drupal\Core\Session\AccountInterface $account
562
 *   The account trying to access the entity.
563
 *
564
 * @return \Drupal\Core\Access\AccessResultInterface
565 566 567 568 569 570 571 572
 *   The access result. The final result is calculated by using
 *   \Drupal\Core\Access\AccessResultInterface::orIf() on the result of every
 *   hook_entity_access() and hook_ENTITY_TYPE_access() implementation, and the
 *   result of the entity-specific checkAccess() method in the entity access
 *   control handler. Be careful when writing generalized access checks shared
 *   between routing and entity checks: routing uses the andIf() operator. So
 *   returning an isNeutral() does not determine entity access at all but it
 *   always ends up denying access while routing.
573
 *
574
 * @see \Drupal\Core\Entity\EntityAccessControlHandler
575 576 577 578
 * @see hook_entity_create_access()
 * @see hook_ENTITY_TYPE_access()
 *
 * @ingroup entity_api
579
 */
580
function hook_entity_access(\Drupal\Core\Entity\EntityInterface $entity, $operation, \Drupal\Core\Session\AccountInterface $account) {
581
  // No opinion.
582
  return AccessResult::neutral();
583 584 585 586 587 588 589 590 591 592
}

/**
 * Control entity operation access for a specific entity type.
 *
 * @param \Drupal\Core\Entity\EntityInterface $entity
 *   The entity to check access to.
 * @param string $operation
 *   The operation that is to be performed on $entity.
 * @param \Drupal\Core\Session\AccountInterface $account
593
 *   The account trying to access the entity.
594
 *
595
 * @return \Drupal\Core\Access\AccessResultInterface
596
 *   The access result. hook_entity_access() has detailed documentation.
597
 *
598
 * @see \Drupal\Core\Entity\EntityAccessControlHandler
599 600 601 602
 * @see hook_ENTITY_TYPE_create_access()
 * @see hook_entity_access()
 *
 * @ingroup entity_api
603
 */
604
function hook_ENTITY_TYPE_access(\Drupal\Core\Entity\EntityInterface $entity, $operation, \Drupal\Core\Session\AccountInterface $account) {
605
  // No opinion.
606
  return AccessResult::neutral();
607 608 609 610 611 612
}

/**
 * Control entity create access.
 *
 * @param \Drupal\Core\Session\AccountInterface $account
613
 *   The account trying to access the entity.
614
 * @param array $context
615
 *   An associative array of additional context values. By default it contains
616 617
 *   language and the entity type ID:
 *   - entity_type_id - the entity type ID.
618
 *   - langcode - the current language code.
619
 * @param string $entity_bundle
620
 *   The entity bundle name.
621
 *
622
 * @return \Drupal\Core\Access\AccessResultInterface
623
 *   The access result.
624
 *
625
 * @see \Drupal\Core\Entity\EntityAccessControlHandler
626 627 628 629
 * @see hook_entity_access()
 * @see hook_ENTITY_TYPE_create_access()
 *
 * @ingroup entity_api
630
 */
631
function hook_entity_create_access(\Drupal\Core\Session\AccountInterface $account, array $context, $entity_bundle) {
632
  // No opinion.
633
  return AccessResult::neutral();
634 635 636 637 638 639
}

/**
 * Control entity create access for a specific entity type.
 *
 * @param \Drupal\Core\Session\AccountInterface $account
640
 *   The account trying to access the entity.
641
 * @param array $context
642 643 644
 *   An associative array of additional context values. By default it contains
 *   language:
 *   - langcode - the current language code.
645
 * @param string $entity_bundle
646
 *   The entity bundle name.
647
 *
648
 * @return \Drupal\Core\Access\AccessResultInterface
649
 *   The access result.
650
 *
651
 * @see \Drupal\Core\Entity\EntityAccessControlHandler
652 653 654 655
 * @see hook_ENTITY_TYPE_access()
 * @see hook_entity_create_access()
 *
 * @ingroup entity_api
656
 */
657
function hook_ENTITY_TYPE_create_access(\Drupal\Core\Session\AccountInterface $account, array $context, $entity_bundle) {
658
  // No opinion.
659
  return AccessResult::neutral();
660 661
}

662
/**
663 664
 * Add to entity type definitions.
 *
665 666
 * Modules may implement this hook to add information to defined entity types,
 * as defined in \Drupal\Core\Entity\EntityTypeInterface.
667
 *
668 669 670
 * To alter existing information or to add information dynamically, use
 * hook_entity_type_alter().
 *
671
 * @param \Drupal\Core\Entity\EntityTypeInterface[] $entity_types
672 673 674 675
 *   An associative array of all entity type definitions, keyed by the entity
 *   type name. Passed by reference.
 *
 * @see \Drupal\Core\Entity\Entity
676
 * @see \Drupal\Core\Entity\EntityTypeInterface
677
 * @see hook_entity_type_alter()
678
 */
679 680
function hook_entity_type_build(array &$entity_types) {
  /** @var $entity_types \Drupal\Core\Entity\EntityTypeInterface[] */
681
  // Add a form for a custom node form without overriding the default
682
  // node form. To override the default node form, use hook_entity_type_alter().
683
  $entity_types['node']->setFormClass('mymodule_foo', 'Drupal\mymodule\NodeFooForm');
684 685
}

686 687 688 689 690 691 692 693
/**
 * Alter the entity type definitions.
 *
 * Modules may implement this hook to alter the information that defines an
 * entity type. All properties that are available in
 * \Drupal\Core\Entity\Annotation\EntityType and all the ones additionally
 * provided by modules can be altered here.
 *
694 695 696 697 698 699
 * Do not use this hook to add information to entity types, unless one of the
 * following is true:
 * - You are filling in default values.
 * - You need to dynamically add information only in certain circumstances.
 * - Your hook needs to run after hook_entity_type_build() implementations.
 * Use hook_entity_type_build() instead in all other cases.
700
 *
701
 * @param \Drupal\Core\Entity\EntityTypeInterface[] $entity_types
702 703 704 705 706 707
 *   An associative array of all entity type definitions, keyed by the entity
 *   type name. Passed by reference.
 *
 * @see \Drupal\Core\Entity\Entity
 * @see \Drupal\Core\Entity\EntityTypeInterface
 */
708 709
function hook_entity_type_alter(array &$entity_types) {
  /** @var $entity_types \Drupal\Core\Entity\EntityTypeInterface[] */
710
  // Set the controller class for nodes to an alternate implementation of the
711 712
  // Drupal\Core\Entity\EntityStorageInterface interface.
  $entity_types['node']->setStorageClass('Drupal\mymodule\MyCustomNodeStorage');
713 714
}

715 716 717 718 719 720
/**
 * Alter the view modes for entity types.
 *
 * @param array $view_modes
 *   An array of view modes, keyed first by entity type, then by view mode name.
 *
721 722
 * @see \Drupal\Core\Entity\EntityManagerInterface::getAllViewModes()
 * @see \Drupal\Core\Entity\EntityManagerInterface::getViewModes()
723 724
 */
function hook_entity_view_mode_info_alter(&$view_modes) {
725
  $view_modes['user']['full']['status'] = TRUE;
726 727 728 729 730 731 732 733 734 735 736 737 738
}

/**
 * Describe the bundles for entity types.
 *
 * @return array
 *   An associative array of all entity bundles, keyed by the entity
 *   type name, and then the bundle name, with the following keys:
 *   - label: The human-readable name of the bundle.
 *   - uri_callback: The same as the 'uri_callback' key defined for the entity
 *     type in the EntityManager, but for the bundle only. When determining
 *     the URI of an entity, if a 'uri_callback' is defined for both the
 *     entity type and the bundle, the one for the bundle is used.
739 740
 *   - translatable: (optional) A boolean value specifying whether this bundle
 *     has translation support enabled. Defaults to FALSE.
741
 *
742
 * @see \Drupal\Core\Entity\EntityTypeBundleInfo::getBundleInfo()
743 744 745
 * @see hook_entity_bundle_info_alter()
 */
function hook_entity_bundle_info() {
746
  $bundles['user']['user']['label'] = t('User');
747 748 749 750 751 752 753 754 755
  return $bundles;
}

/**
 * Alter the bundles for entity types.
 *
 * @param array $bundles
 *   An array of bundles, keyed first by entity type, then by bundle name.
 *
756
 * @see Drupal\Core\Entity\EntityTypeBundleInfo::getBundleInfo()
757 758 759 760
 * @see hook_entity_bundle_info()
 */
function hook_entity_bundle_info_alter(&$bundles) {
  $bundles['user']['user']['label'] = t('Full account');
761 762
}

763 764 765 766 767
/**
 * Act on entity_bundle_create().
 *
 * This hook is invoked after the operation has been performed.
 *
768
 * @param string $entity_type_id
769 770 771
 *   The type of $entity; e.g. 'node' or 'user'.
 * @param string $bundle
 *   The name of the bundle.
772 773
 *
 * @see entity_crud
774
 */
775
function hook_entity_bundle_create($entity_type_id, $bundle) {
776 777
  // When a new bundle is created, the menu needs to be rebuilt to add the
  // Field UI menu item tabs.
778
  \Drupal::service('router.builder')->setRebuildNeeded();
779 780 781 782 783 784 785
}

/**
 * Act on entity_bundle_delete().
 *
 * This hook is invoked after the operation has been performed.
 *
786
 * @param string $entity_type_id
787 788 789
 *   The type of entity; for example, 'node' or 'user'.
 * @param string $bundle
 *   The bundle that was just deleted.
790 791
 *
 * @ingroup entity_crud
792
 */
793
function hook_entity_bundle_delete($entity_type_id, $bundle) {
794
  // Remove the settings associated with the bundle in my_module.settings.
795
  $config = \Drupal::config('my_module.settings');
796
  $bundle_settings = $config->get('bundle_settings');
797 798
  if (isset($bundle_settings[$entity_type_id][$bundle])) {
    unset($bundle_settings[$entity_type_id][$bundle]);
799 800 801 802
    $config->set('bundle_settings', $bundle_settings);
  }
}

803
/**
804
 * Acts when creating a new entity.
805
 *
806
 * This hook runs after a new entity object has just been instantiated.
807 808 809
 *
 * @param \Drupal\Core\Entity\EntityInterface $entity
 *   The entity object.
810 811 812
 *
 * @ingroup entity_crud
 * @see hook_ENTITY_TYPE_create()
813 814
 */
function hook_entity_create(\Drupal\Core\Entity\EntityInterface $entity) {
815
  \Drupal::logger('example')->info('Entity created: @label', ['@label' => $entity->label()]);
816 817
}

818
/**
819
 * Acts when creating a new entity of a specific type.
820
 *
821
 * This hook runs after a new entity object has just been instantiated.
822 823 824 825 826 827 828 829
 *
 * @param \Drupal\Core\Entity\EntityInterface $entity
 *   The entity object.
 *
 * @ingroup entity_crud
 * @see hook_entity_create()
 */
function hook_ENTITY_TYPE_create(\Drupal\Core\Entity\EntityInterface $entity) {
830
  \Drupal::logger('example')->info('ENTITY_TYPE created: @label', ['@label' => $entity->label()]);
831 832
}

833 834 835 836 837 838
/**
 * Act on entities when loaded.
 *
 * This is a generic load hook called for all entity types loaded via the
 * entity API.
 *
839 840 841 842
 * hook_entity_storage_load() should be used to load additional data for
 * content entities.
 *
 * @param \Drupal\Core\Entity\EntityInterface[] $entities
843
 *   The entities keyed by entity ID.
844
 * @param string $entity_type_id
845
 *   The type of entities being loaded (i.e. node, user, comment).
846 847 848
 *
 * @ingroup entity_crud
 * @see hook_ENTITY_TYPE_load()
849
 */
850
function hook_entity_load(array $entities, $entity_type_id) {
851
  foreach ($entities as $entity) {
852
    $entity->foo = mymodule_add_something($entity);
853 854 855 856
  }
}

/**
857 858 859 860 861 862 863 864 865 866 867 868 869 870
 * Act on entities of a specific type when loaded.
 *
 * @param array $entities
 *   The entities keyed by entity ID.
 *
 * @ingroup entity_crud
 * @see hook_entity_load()
 */
function hook_ENTITY_TYPE_load($entities) {
  foreach ($entities as $entity) {
    $entity->foo = mymodule_add_something($entity);
  }
}

871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904
/**
 * Act on content entities when loaded from the storage.
 *
 * The results of this hook will be cached.
 *
 * @param \Drupal\Core\Entity\EntityInterface[] $entities
 *   The entities keyed by entity ID.
 * @param string $entity_type
 *   The type of entities being loaded (i.e. node, user, comment).
 *
 * @see hook_entity_load()
 */
function hook_entity_storage_load(array $entities, $entity_type) {
  foreach ($entities as $entity) {
    $entity->foo = mymodule_add_something_uncached($entity);
  }
}

/**
 * Act on content entities of a given type when loaded from the storage.
 *
 * The results of this hook will be cached if the entity type supports it.
 *
 * @param \Drupal\Core\Entity\EntityInterface[] $entities
 *   The entities keyed by entity ID.
 *
 * @see hook_entity_storage_load()
 */
function hook_ENTITY_TYPE_storage_load(array $entities) {
  foreach ($entities as $entity) {
    $entity->foo = mymodule_add_something_uncached($entity);
  }
}

905 906
/**
 * Act on an entity before it is created or updated.
907
 *
908 909 910
 * You can get the original entity object from $entity->original when it is an
 * update of the entity.
 *
911
 * @param \Drupal\Core\Entity\EntityInterface $entity
912
 *   The entity object.
913 914 915
 *
 * @ingroup entity_crud
 * @see hook_ENTITY_TYPE_presave()
916
 */
917
function hook_entity_presave(Drupal\Core\Entity\EntityInterface $entity) {
918 919 920
  if ($entity instanceof ContentEntityInterface && $entity->isTranslatable()) {
    $route_match = \Drupal::routeMatch();
    \Drupal::service('content_translation.synchronizer')->synchronizeFields($entity, $entity->language()->getId(), $route_match->getParameter('source_langcode'));
921 922 923 924 925 926
  }
}

/**
 * Act on a specific type of entity before it is created or updated.
 *
927 928 929
 * You can get the original entity object from $entity->original when it is an
 * update of the entity.
 *
930 931 932 933 934 935 936 937
 * @param \Drupal\Core\Entity\EntityInterface $entity
 *   The entity object.
 *
 * @ingroup entity_crud
 * @see hook_entity_presave()
 */
function hook_ENTITY_TYPE_presave(Drupal\Core\Entity\EntityInterface $entity) {
  if ($entity->isTranslatable()) {
938 939
    $route_match = \Drupal::routeMatch();
    \Drupal::service('content_translation.synchronizer')->synchronizeFields($entity, $entity->language()->getId(), $route_match->getParameter('source_langcode'));
940
  }
941 942 943
}

/**
944 945 946 947
 * Respond to creation of a new entity.
 *
 * This hook runs once the entity has been stored. Note that hook
 * implementations may not alter the stored entity data.
948
 *
949
 * @param \Drupal\Core\Entity\EntityInterface $entity
950
 *   The entity object.
951 952 953
 *
 * @ingroup entity_crud
 * @see hook_ENTITY_TYPE_insert()
954
 */
955
function hook_entity_insert(Drupal\Core\Entity\EntityInterface $entity) {
956 957
  // Insert the new entity into a fictional table of all entities.
  db_insert('example_entity')
958
    ->fields([
959
      'type' => $entity->getEntityTypeId(),
960
      'id' => $entity->id(),
961 962
      'created' => REQUEST_TIME,
      'updated' => REQUEST_TIME,
963
    ])
964 965 966
    ->execute();
}

967 968 969 970 971 972 973 974 975 976 977 978 979 980 981
/**
 * Respond to creation of a new entity of a particular type.
 *
 * This hook runs once the entity has been stored. Note that hook
 * implementations may not alter the stored entity data.
 *
 * @param \Drupal\Core\Entity\EntityInterface $entity
 *   The entity object.
 *
 * @ingroup entity_crud
 * @see hook_entity_insert()
 */
function hook_ENTITY_TYPE_insert(Drupal\Core\Entity\EntityInterface $entity) {
  // Insert the new entity into a fictional table of this type of entity.
  db_insert('example_entity')
982
    ->fields([
983 984 985
      'id' => $entity->id(),
      'created' => REQUEST_TIME,
      'updated' => REQUEST_TIME,
986
    ])
987 988 989
    ->execute();
}

990
/**
991 992 993
 * Respond to updates to an entity.
 *
 * This hook runs once the entity storage has been updated. Note that hook
994 995
 * implementations may not alter the stored entity data. Get the original entity
 * object from $entity->original.
996
 *
997
 * @param \Drupal\Core\Entity\EntityInterface $entity
998
 *   The entity object.
999 1000 1001
 *
 * @ingroup entity_crud
 * @see hook_ENTITY_TYPE_update()
1002
 */
1003
function hook_entity_update(Drupal\Core\Entity\EntityInterface $entity) {
1004 1005
  // Update the entity's entry in a fictional table of all entities.
  db_update('example_entity')
1006
    ->fields([
1007
      'updated' => REQUEST_TIME,
1008
    ])
1009
    ->condition('type', $entity->getEntityTypeId())
1010
    ->condition('id', $entity->id())
1011 1012 1013
    ->execute();
}

1014 1015 1016 1017
/**
 * Respond to updates to an entity of a particular type.
 *
 * This hook runs once the entity storage has been updated. Note that hook
1018 1019
 * implementations may not alter the stored entity data. Get the original entity
 * object from $entity->original.
1020 1021 1022 1023 1024 1025 1026 1027 1028 1029
 *
 * @param \Drupal\Core\Entity\EntityInterface $entity
 *   The entity object.
 *
 * @ingroup entity_crud
 * @see hook_entity_update()
 */
function hook_ENTITY_TYPE_update(Drupal\Core\Entity\EntityInterface $entity) {
  // Update the entity's entry in a fictional table of this type of entity.
  db_update('example_entity')
1030
    ->fields([
1031
      'updated' => REQUEST_TIME,
1032
    ])
1033 1034 1035 1036
    ->condition('id', $entity->id())
    ->execute();
}

1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068
/**
 * Acts when creating a new entity translation.
 *
 * This hook runs after a new entity translation object has just been
 * instantiated.
 *
 * @param \Drupal\Core\Entity\EntityInterface $translation
 *   The entity object.
 *
 * @ingroup entity_crud
 * @see hook_ENTITY_TYPE_translation_create()
 */
function hook_entity_translation_create(\Drupal\Core\Entity\EntityInterface $translation) {
  \Drupal::logger('example')->info('Entity translation created: @label', ['@label' => $translation->label()]);
}

/**
 * Acts when creating a new entity translation of a specific type.
 *
 * This hook runs after a new entity translation object has just been
 * instantiated.
 *
 * @param \Drupal\Core\Entity\EntityInterface $translation
 *   The entity object.
 *
 * @ingroup entity_crud
 * @see hook_entity_translation_create()
 */
function hook_ENTITY_TYPE_translation_create(\Drupal\Core\Entity\EntityInterface $translation) {
  \Drupal::logger('example')->info('ENTITY_TYPE translation created: @label', ['@label' => $translation->label()]);
}

1069
/**
1070 1071 1072 1073
 * Respond to creation of a new entity translation.
 *
 * This hook runs once the entity translation has been stored. Note that hook
 * implementations may not alter the stored entity translation data.
1074 1075 1076
 *
 * @param \Drupal\Core\Entity\EntityInterface $translation
 *   The entity object of the translation just stored.
1077 1078 1079
 *
 * @ingroup entity_crud
 * @see hook_ENTITY_TYPE_translation_insert()
1080 1081
 */
function hook_entity_translation_insert(\Drupal\Core\Entity\EntityInterface $translation) {
1082
  $variables = [
1083
    '@language' => $translation->language()->getName(),
1084
    '@label' => $translation->getUntranslated()->label(),
1085
  ];
1086
  \Drupal::logger('example')->notice('The @language translation of @label has just been stored.', $variables);
1087 1088
}

1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101
/**
 * Respond to creation of a new entity translation of a particular type.
 *
 * This hook runs once the entity translation has been stored. Note that hook
 * implementations may not alter the stored entity translation data.
 *
 * @param \Drupal\Core\Entity\EntityInterface $translation
 *   The entity object of the translation just stored.
 *
 * @ingroup entity_crud
 * @see hook_entity_translation_insert()
 */
function hook_ENTITY_TYPE_translation_insert(\Drupal\Core\Entity\EntityInterface $translation) {
1102
  $variables = [
1103
    '@language' => $translation->language()->getName(),
1104
    '@label' => $translation->getUntranslated()->label(),
1105
  ];
1106 1107 1108
  \Drupal::logger('example')->notice('The @language translation of @label has just been stored.', $variables);
}

1109
/**
1110 1111 1112
 * Respond to entity translation deletion.
 *
 * This hook runs once the entity translation has been deleted from storage.
1113
 *
1114
 * @param \Drupal\Core\Entity\EntityInterface $translation
1115
 *   The original entity object.
1116 1117 1118
 *
 * @ingroup entity_crud
 * @see hook_ENTITY_TYPE_translation_delete()
1119 1120
 */
function hook_entity_translation_delete(\Drupal\Core\Entity\EntityInterface $translation) {
1121
  $variables = [
1122 1123
    '@language' => $translation->language()->getName(),
    '@label' => $translation->label(),
1124
  ];
1125
  \Drupal::logger('example')->notice('The @language translation of @label has just been deleted.', $variables);
1126 1127
}

1128 1129 1130 1131 1132
/**
 * Respond to entity translation deletion of a particular type.
 *
 * This hook runs once the entity translation has been deleted from storage.
 *
1133
 * @param \Drupal\Core\Entity\EntityInterface $translation
1134 1135 1136 1137 1138 1139
 *   The original entity object.
 *
 * @ingroup entity_crud
 * @see hook_entity_translation_delete()
 */
function hook_ENTITY_TYPE_translation_delete(\Drupal\Core\Entity\EntityInterface $translation) {
1140
  $variables = [
1141 1142
    '@language' => $translation->language()->getName(),
    '@label' => $translation->label(),
1143
  ];
1144 1145 1146
  \Drupal::logger('example')->notice('The @language translation of @label has just been deleted.', $variables);
}

1147
/**
1148 1149
 * Act before entity deletion.
 *
1150
 * @param \Drupal\Core\Entity\EntityInterface $entity