Current user route redirects without context param in REST API

[edygardelima]

In the REST API, the context param is ignored when trying to reach to current user through wp/v2/users/me. Turns out the route it redirects to wp/v2/users/[id] but misses any given param.

[ocean90]

Hello @edygardelima, welcome to the WordPress Trac!

Thanks for your report, @dd32 had ​the same question on Slack today.

[jnylen0]

Quoting from the Slack link above - the actual issue here is a bit different now that we're not doing this redirect any more:

Any specific reason /users/1 is context=view while /users/me is context=embed? Causes it to skip at least registered meta fields from the /me response

/me was only a recently addition (used to 301) so it might have been an oversight from then

[danielbachhuber]

GET /wp/v2/users/me defaults to context=view in trunk.

Attaching a patch that asserts this in the tests. The original report isn't valid.

[danielbachhuber]

Assert context=view by default for GET /wp/v2/users/me

[rachelbaker]

Looks like the context param was recently fixed as a part of #38792

[rachelbaker]

In 39293:

REST API: Add test case for users/me endpoint that the context param defaults to view.

Props danielbachhuber.
See #38842.