From 8f1c5372f72db044c5ec37c161a7f180853a8be9 Mon Sep 17 00:00:00 2001 From: catch <catch@35733.no-reply.drupal.org> Date: Wed, 22 Feb 2023 13:35:27 +0000 Subject: [PATCH] Issue #2910181 by sarvjeetsingh, anmolgoyal74, apaderno, pameeela, jcalais: Update hook_node_grants docs to remove role ID reference, since it is no longer an integer (cherry picked from commit 8d2e488062e094e9e285b001031463110414b357) --- core/modules/node/node.api.php | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/core/modules/node/node.api.php b/core/modules/node/node.api.php index face0558d241..8b01c6632397 100644 --- a/core/modules/node/node.api.php +++ b/core/modules/node/node.api.php @@ -22,11 +22,8 @@ * "realms". In hook_node_access_records(), the realms and grant IDs are * associated with permission to view, edit, and delete individual nodes. * - * The realms and grant IDs can be arbitrarily defined by your node access - * module; it is common to use role IDs as grant IDs, but that is not required. - * Your module could instead maintain its own list of users, where each list has - * an ID. In that case, the return value of this hook would be an array of the - * list IDs that this user is a member of. + * Grant IDs can be arbitrarily defined by a node access module using a list of + * integer IDs associated with users. * * A node access module may implement as many realms as necessary to properly * define the access privileges for the nodes. Note that the system makes no -- GitLab