From 228c200b35e0d71a8c0ce518bb82c00868ddaa48 Mon Sep 17 00:00:00 2001 From: Drew Jaynes Date: Wed, 16 Dec 2015 05:31:27 +0000 Subject: [PATCH] Docs: Add variadic markers to the optional `$object_id` parameter notation for `WP_User::has_cap()`. See #32246. git-svn-id: https://develop.svn.wordpress.org/trunk@35954 602fd350-edb4-49c9-b593-d223f7449a82 --- src/wp-includes/class-wp-user.php | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/src/wp-includes/class-wp-user.php b/src/wp-includes/class-wp-user.php index 91dc5a7e93..8a2ed09e27 100644 --- a/src/wp-includes/class-wp-user.php +++ b/src/wp-includes/class-wp-user.php @@ -701,12 +701,12 @@ class WP_User { * * @see map_meta_cap() * - * @param string $cap Capability name. - * @param int $object_id Optional. ID of the specific object to check against if `$cap` is a "meta" cap. - * "Meta" capabilities, e.g. 'edit_post', 'edit_user', etc., are capabilities used - * by map_meta_cap() to map to other "primitive" capabilities, e.g. 'edit_posts', - * 'edit_others_posts', etc. The parameter is accessed via func_get_args() and passed - * to map_meta_cap(). + * @param string $cap Capability name. + * @param int $object_id,... Optional. ID of the specific object to check against if `$cap` is a "meta" cap. + * "Meta" capabilities, e.g. 'edit_post', 'edit_user', etc., are capabilities used + * by map_meta_cap() to map to other "primitive" capabilities, e.g. 'edit_posts', + * 'edit_others_posts', etc. The parameter is accessed via func_get_args() and passed + * to map_meta_cap(). * @return bool Whether the current user has the given capability. If `$cap` is a meta cap and `$object_id` is * passed, whether the current user has the given meta capability for the given object. */