The schema for the taxonomy property of a term in the REST API should not include all taxonomies

[johnbillion]

When performing an OPTIONS request to a term endpoint of the REST API, for example /wp-json/wp/v2/tags or /wp-json/wp/v2/categories, the $.schema.properties.taxonomy.enum property in the schema contains a list of names of all taxonomies on the site (and to boot, not just those that are exposed via the REST API).

This is incorrect. The enum should contain only one value containing the name of the taxonomy associated with the route.

https://core.trac.wordpress.org/ticket/51940

[TimothyBlynJacobs]

In 49922:

REST API: Only include the controller's own taxonomy in it's schema.

Previously, all taxonomies were incorrectly exposed as possible values.

Props johnbillion.
Fixes #51940.

[TimothyBlynJacobs]

(and to boot, not just those that are exposed via the REST API)

Do you think we should backport this?

https://core.trac.wordpress.org/changeset/49922

[johnbillion]

Yes this is a good candidate for backporting to 4.7.x.

[whyisjake]

In 50047:

REST API: Only include the controller's own taxonomy in it's schema.

Previously, all taxonomies were incorrectly exposed as possible values.

This commit brings the changes from [49922] to the 5.6 branch.

Props johnbillion, TimothyBlynJacobs.

Fixes #51940.