This repository has been archived by the owner on Jul 23, 2024. It is now read-only.
New filter: allow non-core post types in Relationship ACF field #177
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.
The current logic assumes that all post models are instances of the
Post
model. Unfortunately, when non-core post types such as WooCommerce are part of this request, the result is an internal error (see screenshot).This filter would make it possible for extensions to properly set the correct source Type, thereby fulfilling the request. A similar filter already exists (
graphql_acf_post_object_source
) for thepost_object
field type; this new filter tries to follow the same pattern.An example implementation would be identical to
graphql_acf_post_object_source
. See https://github.com/wp-graphql/wp-graphql-woocommerce/blob/develop/includes/class-acf-schema-filters.php#L56Screenshots
Error when no filter is in place 👇🏽
Relationship field filtering only
Product
post type 👇🏽