REST API: Terms endpoint responses for PUT & POST requests don't set context to edit

[westonruter]

The endpoints for posts, users, and comments all set the context to edit when returning the resource in the response for POST and PUT requests. The terms endpoint, however, unexpectedly returns the resource with the view context. In practice this won't cause a problem since all of the fields (in core) have both the view and edit contexts, but if a plugin adds additional fields that should only appear in the edit context then this could cause a problem where the unexpected fields would be returned in the response.

[rmccue]

lgtm, we should add unit tests to check this though.

[kadamwhite]

Accepting for 5.3 as a quick win. I'll look into writing up a test.

[dlh]

41411.1.diff​ adds a test.

[TimothyBlynJacobs]

This looks good to me. The test needs to use traditional array syntax though. I'd also use assertArrayHasKey and assertArrayNotHasKey instead of assertTrue( isset ).

[dlh]

Great catch and great suggestions. Updated in 41411.2.diff​.

[TimothyBlynJacobs]

Looks good!

[kadamwhite]

In 46098:

REST API: Return term resources in "edit" context after PUT or POST request.

Props westonruter, dlh.
Fixes #41411.