Make WP->parse_request() variables more self-descriptive

[ericlewis]

The variable names $req_uri and $request make WP->parse_request() a bit hard to follow.

[ericlewis]

This is related to my question in #18877

The fact that the function requires $request and $request_uri is confusing. I wonder if we can boil the function input down to $request.

We can't boil down the function input to $request, because the rewrite matching engine needs to know what the requested filename as well as the URL path in the case of PATH_INFO links.

[ericlewis]

In attachment:36674.diff​, I suggest using the names $requested_file and $requested_path for clarity.

[ericlewis]

In 37356:

Rewrite Rules: Add self-describing variables to rewrite matcher.

The rewrite rule matching code in WP::parse_request() used an unclear variable $request to represent the requested path (e.g. "2016/05/03") as well as a deceptively named variable $request_uri, which actually represents the requested file when an install used PATHINFO links.

Those variables are replaced with $requested_path and $requested_file respectively for clarity.

Fixes #36674.

[DrewAPicture]

In 37366:

Docs: Remove backticks from the DocBlock summary for WP::$request, added in [37356].

Markdown formatting is not supported in DocBlock summaries, per the inline documentation standards for PHP :-)

See #32246. See #36674.