-
Notifications
You must be signed in to change notification settings - Fork 442
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ancestors to posts/terms #116
Comments
jasonbahl
added a commit
to jasonbahl/wp-graphql
that referenced
this issue
May 23, 2017
jasonbahl
added a commit
to jasonbahl/wp-graphql
that referenced
this issue
May 26, 2017
…o feature/wp-graphql#116-ancestor-support # Conflicts: # src/Type/PostObject/PostObjectType.php # src/Type/TermObject/TermObjectType.php # wp-graphql.php
jasonbahl
added a commit
to jasonbahl/wp-graphql
that referenced
this issue
Jun 23, 2017
…o feature/wp-graphql#116-ancestor-support # Conflicts: # src/Type/TermObject/TermObjectType.php
Merged
Addressed by #157 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should support ancestors for termObjects of hierarchical taxonomies, and for postTypeObjects (any postType can have a parent set, even if it's not explicitly defined as hierarchical, such as "attachment" post_type having the parent of a post or page. . .so the ancestor field for postTypeObjects probably needs to be a postObjectUnion
See get_ancestors: https://developer.wordpress.org/reference/functions/get_ancestors/
The text was updated successfully, but these errors were encountered: