chore: improve type-safety for WPGraphQL class
#3367
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Code Climate has analyzed commit faa1353 and detected 2 issues on this pull request. Here's the issue category breakdown:
View more on Code Climate. |
justlevine
changed the title
WPGraphQL class
justlevine
added
status: in review
justlevine
added
type: chore
jasonbahl
approved these changes
Apr 28, 2025
jasonbahl
pushed a commit
to justlevine/wp-graphql
that referenced
this pull request
Apr 28, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 does this implement/fix? Explain your changes.
This PR:
mixedwith the specific array shape (where possible)WPGraphQL::get_allowed_post_types()and::get_allowed_taxonomies(), so the correct traversable type of the array is hinted correctly.References to these functions have been cleaned up accordingly (usually just by removing a
/** @var {...} */typehint.There are no breaking changes in this PR.
Does this close any currently open issues?
Any other comments?