-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
Suggestion for possible Typing Improvements #119
Comments
Based on the Readme it looks like not all {
nodeByUri(uri: "/blog/post-1/") {
... on TermNodeWithSeo {
seo {
...SeoData
}
}
... on ContentNodeWithSeo {
seo {
...SeoData
}
}
}
} |
Looks like the |
@moonmeister This seems like a really good idea! |
Thanks, I unfortunately don't have much for PHP skills...so can't help with implementation. I also had the though that |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days |
Not stale |
@ashhitch would love to help with this, PMing you on the wp-graphql slack |
Sorry really need to remove this action |
I was trying to abstract my SEO information into my layout so I didn't have to repeat myself in each post/page/tag/category/etc template. The query I started writing looks like this:
This seems extremely verbose given the same fields are available on all (or so I suppose). WPGraphQL already has types that solve this issue for things like Title/Author/etc:
What I'm recommending is we create type like
NodeWithSeo
for yoast:Thoughts?
The text was updated successfully, but these errors were encountered: