feat: add graphql_pre_resolve_menu_item_connected_node filter
#3044
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 adds the
graphql_pre_resolve_menu_item_connected_nodefilter to theMenuItem.connectedNoderesolver, allowing one to short-circuit the resolver logic and use a customAbstractConnectionResolver->get_connection()as the result.Additionally, the
graphql_resolve_menu_itemfilter on the deprecatedMenuItem.connectedObjectresolver has beendeprecated.This change brings parity between
connectedNodeandconnectedObject, and will allow developers still relying on the latter to finally migrate.Tests have been added both to cover the new filter, and to cover resolving
TermObjects (since that was missing).Does this close any currently open issues?
Fixes #2484
Any relevant logs, error output, GraphiQL screenshots, etc?
Any other comments?
@todotag that will need to be replaced on release and will need to be replaced manually (its not in the usual@since @todoformat.Where has this been tested?
Operating System: Ubuntu 20.04 (wsl2 + devilbox + php8.1.14)
WordPress Version: 6.4.3