feat: allow global/database IDs in Post connection where args ID inputs#2525
Merged
jasonbahl merged 9 commits intowp-graphql:developfrom Sep 19, 2022
Merged
Conversation
| * | ||
| * @return array | ||
| */ | ||
| public function get_args() { |
There was a problem hiding this comment.
Function get_args has a Cognitive Complexity of 13 (exceeds 5 allowed). Consider refactoring.
|
Code Climate has analyzed commit 69dfe67 and detected 2 issues on this pull request. Here's the issue category breakdown:
View more on Code Climate. |
9 tasks
jasonbahl
approved these changes
Sep 19, 2022
Merged
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
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 allows Term connection where args with a type ID to accept either global IDs or database IDs.
Additionally, the descriptions of
tagSlugAndandtagSlugInhave been updated to better convey what they actually do.This PR replaces #2340 , and requires #2521 to be merged as a prerequisite.
Does this close any currently open issues?
Part of #998
Any relevant logs, error output, GraphiQL screenshots, etc?
(If it’s long, please paste to https://ghostbin.com/ and insert the link here.)
Any other comments?
postsare inPostObjectConnectionQueriesTestsand for a singularpostinPostObjectQueriesTest.dateQueryormimeType- because I was running out of time and didnt want to :-P . They're not essential to this PR (and no code changes to those inputs have been made), and imo we shouldnt hold up merging this and closing Update Resolvers for all ID inputs to behave consistently #998 until I have a break from client work.Where has this been tested?
Operating System: Ubuntu 20.04 (wsl2 + devilbox + PHP 8.0.19)
WordPress Version: 6.0.2