Function clarity; Rename wp_get_user_request_data to wp_get_user_request as it returns the WP_User_Request

[garrett-eclipse]

This is a follow-up to #44708.

In 5.1 changeset 44606 renamed variables from $request_data to $request. After a quick scrub it seems some were overlooked or are new.

Instances;
3 occurrences in the wp_create_user_request function - ​https://github.com/WordPress/WordPress/blob/50ddffbac37fdae9298d1f11fe1dd7b8535fc839/wp-includes/user.php#L3309-L3347
2 occurrences in the WP_User_Request class - ​https://github.com/WordPress/WordPress/blob/50ddffbac37fdae9298d1f11fe1dd7b8535fc839/wp-includes/user.php#L3712-L3738

I'm unsure if the instances in the class should be changed or not as the other changes were because the variable was held the entire class while this instance is a property of that class.

And a last thought was should the wp_get_user_request_data not be wp_get_user_request and it's docblock state 'Return the user request.' simply because it's a function to get the request itself and not just the request_data.
The function I mentioned - ​https://github.com/WordPress/WordPress/blob/50ddffbac37fdae9298d1f11fe1dd7b8535fc839/wp-includes/user.php#L3617-L3634

Thanks

[garrett-eclipse]

Initial patch to correct the wp_get_user_request_data function as it returns the request and not the request_data which is a property of the WP_User_Request

[garrett-eclipse]

Coming back to review the instances of $request_data I'd initially flagged were valid as they represented the array form of request data. The wp_get_user_request_data function on the other hand specifically returns the WP_User_Request object which in itself has a $request_data property. To avoid confusion with this I've uploaded an initial patch to update the function to wp_get_user_request in order to clarify it's purpose. To maintain back-compat I've deprecated the function.

Please review and test, so far beyond throwing the deprecation warning with use of the old function there's no change to the request functionality.

Flagging for testing and dev-note.

[garrett-eclipse]

Note... ignore the mismatch of patch number to ticket number. It's the right patch I just saved it as the wrong number.

[SergeyBiryukov]

In 47245:

Privacy: Rename wp_get_user_request_data() to wp_get_user_request() for clarity; deprecate the old function.

The function returns an instance of the WP_User_Request object itself, not its $request_data property.

Follow-up to [44606].

Props garrett-eclipse.
Fixes #46302.

[garrett-eclipse]

Dev Note: ​https://make.wordpress.org/core/2020/03/02/privacy-updates-in-5-4/

[johnjamesjacoby]

I believe this was erroneously deprecated into:

/wp-admin/includes/deprecated.php

instead of:

/wp-includes/deprecated.php.

Both the original function and the new one are available outside of WordPress admin, but the deprecated function is now only available within WordPress admin, which is a back-compat break.

See: ​https://buddypress.trac.wordpress.org/ticket/8265

@SergeyBiryukov Reopen, or create a new issue for 5.4.1?

[garrett-eclipse]

Thanks @johnjamesjacoby I appreciate you catching that and apologize for breaking buddypress.

As this was committed in 5.4 this back-compat issue should be handled in a new ticket which I've created and patched in #49802