You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 24, 2018. It is now read-only.
As a less confusing way of using taxonomies, we should add /taxonomies and /taxonomies/<tax> for the global information about these. We can then include a types parameter (probably what I intended for #197) that links out to both /posts/types/<type>/taxonomies/<tax> and /posts/types/<type>/taxonomies/<tax>/terms
The text was updated successfully, but these errors were encountered:
It is frequently desirable to know about all taxonomies, regardless
of the post type to which they are associated; it is also convenient
to be able to retrieve taxonomies from a base-level endpoint.
This adds the following routes to the taxonomies class:
- /taxonomies
- /taxonomies/(?P<taxonomy>\w+)
- /taxonomies/(?P<taxonomy>\w+)/terms
- /taxonomies/(?P<taxonomy>\w+)/terms/(?P<term>\w+)
Bug Reference: WP-API#198
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As a less confusing way of using taxonomies, we should add
/taxonomies
and/taxonomies/<tax>
for the global information about these. We can then include atypes
parameter (probably what I intended for #197) that links out to both/posts/types/<type>/taxonomies/<tax>
and/posts/types/<type>/taxonomies/<tax>/terms
The text was updated successfully, but these errors were encountered: