From 9059bd722bf23fb4f37e1ed5c13777a1233d12ea Mon Sep 17 00:00:00 2001
From: Lauri Eskola <lauri.eskola@acquia.com>
Date: Wed, 27 Sep 2023 19:19:01 +0300
Subject: [PATCH] Issue #3275828 by joachim, quietone, bradjones1, Berdir:
document the reason for 'edit' vs. 'update' operations in field and entity
access operation name
---
.../Core/Entity/EntityAccessControlHandlerInterface.php | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/core/lib/Drupal/Core/Entity/EntityAccessControlHandlerInterface.php b/core/lib/Drupal/Core/Entity/EntityAccessControlHandlerInterface.php
index 5532996b2d99..92e09562d54f 100644
--- a/core/lib/Drupal/Core/Entity/EntityAccessControlHandlerInterface.php
+++ b/core/lib/Drupal/Core/Entity/EntityAccessControlHandlerInterface.php
@@ -86,8 +86,9 @@ public function setModuleHandler(ModuleHandlerInterface $module_handler);
* \Drupal\Core\Entity\EntityAccessControlHandlerInterface::access().
*
* @param string $operation
- * The operation access should be checked for.
- * Usually one of "view" or "edit".
+ * The operation access should be checked for. Usually one of "view" or
+ * "edit". Unlike entity access, for field access there is no distinction
+ * between creating and updating.
* @param \Drupal\Core\Field\FieldDefinitionInterface $field_definition
* The field definition.
* @param \Drupal\Core\Session\AccountInterface $account
--
GitLab