fix: replace deprecated AbstractConnectionResolver::setQueryArg() call with ::set_query_arg()
#3006
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
…nnectedTaxonomies`
|
Code Climate has analyzed commit a3510a4 and detected 0 issues on this pull request. View more on Code Climate. |
justlevine
added
type: bug
justlevine
changed the title
setQueryArg() with set_query_arg()AbstractConnectionResolver::setQueryArg() call with ::set_query_arg()
Collaborator
Author
|
@jasonbahl can you review this when you get a minute? |
jasonbahl
approved these changes
Jan 23, 2024
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 replaces the deprecated call to
AbstractConnectionResolver::setQueryArg()inContentType.connectedTaxonomiesresolver withAbstractConnectionResolver::set_query_arg().Does this close any currently open issues?
Any relevant logs, error output, GraphiQL screenshots, etc?
Any other comments?
…
Where has this been tested?
Operating System: Ubuntu 20.04 (wsl2 + devilbox + php8.1.15)
WordPress Version: 6.4.2