Coding consistency, seeing both $request and $request_data

[garrett-eclipse]

Hello,

I'm noticing the variable naming for Privacy component items isn't consistent as there's a mix of both $request and $request_data for the request object. IMHO $request makes the most sense.

You can see this inconsistency best when you search for the 'wp_get_user_request_data' function call;
​https://github.com/WordPress/WordPress/search?q=wp_get_user_request_data&unscoped_q=wp_get_user_request_data

$request_data is used in wp-includes/user.php and once in wp-admin/includes/user.php, but $request is found in wp-admin/includes/user.php, wp-admin/includes/file.php and /wp-admin/includes/ajax-actions.php

Cheers

[nateallen]

Changes variables named $request_data to $request for consistency

[bruceallen]

Tested original patch and it looks good in terms of replacing the variables. Doing further testing on functionality.

[garrett-eclipse]

@pento the 44708.diff from @bruceallen seems to have gotten some unrelated css in list-tables.css that shouldn't be there. Aside from that the other changes are identical to 44708.patch from @nateallen so would use that version for the commit.

[desrosj]

In 44606:

Privacy: Use consistent variable naming when working with privacy requests.

Throughout the core privacy functions, WP_User_Request instances were stored in variables named both $request, and $request_data. This changes all occurrences of $request_data to $request for better consistency.

Props nateallen, bruceallen, garrett-eclipse.
Fixes #44708.

[garrett-eclipse]

I've opened #46302 as I found more instances of $request_data. And am also wondering if wp_get_user_request_data shouldn't just be wp_get_user_request as it returns the WP_User_Request object.