dev: add GraphQL Debug message to response when attempting to use Page.seo
for the Posts Archive.
#113
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
This PR adds a
graphql_debug()
message whennull
is returned from aPage.seo
on the Posts archiveWhy
Since WPGraphQL doesn't have an archive type, it treats the
page_for_posts
WP_Post object as aContentType
instead of content node. ( See the discussion on #2486 ).As that's not readily obvious, a debug message directing them to use
contentType
ornodeByUri
will let them know that it's returning null for a reason.Closes #111
How
If the URI is null and the a
Post
model is for the Posts Page, logs a message toextensions.debug
Testing Instructions
Additional Info
Checklist: