-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
release: v2.0.0 beta.5.0.0 #88
Merged
Merged
Conversation
This file contains 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
…graphql_field_name" - add support for OptionsPage UI from ACF v6.2+
…ks is v1.2.0 or later
- add 'wpgraphql/acf/type_registry/init' hook - use get_parent_graphql_type_name on repeater, group and flex field field types
…v2.0.0-beta.5.0.0 # Conflicts: # src/FieldType/Taxonomy.php
- add TestcloneFieldsCest.php
…lution - update WPgraphQLContentBlocks to register all ACF Blocks - remove wpunit test for testClonedFieldGroupIsAppliedAsInterface - introduced Clone Field interface tests as functional tests
….0.0-beta.5.0.0 # Conflicts: # src/LocationRules/LocationRules.php # src/ThirdParty/WPGraphQLContentBlocks/WPGraphQLContentBlocks.php
- add haveAcfProActive test util to be able to run/skip tests if acf pro is not active - update tests to skip if acf pro is not active
Pull Request Test Coverage Report for Build 1d1daf06f8b3c120dbf46c952dfa262e648f5cac-PR-88
💛 - Coveralls |
…tup.sh - remove deleteAllFieldGroups util - remove unused AssertValidSchemaTest
- fix duplicate field issues for types that register connections - remove duplicate config for relationship field
- update how WPGraphQL Content Blocks is installed in app.setup.sh -
…d_config->prepare_acf_field_value()` - apply wpautop to wysiwyg field type - update how connections are cached to ensure they're not registered multiple times in FieldConfig->register_graphql_connections() - update how we bail if WPGraphQL Content Blocks is not active - add test helpers for testing fields against blocks
…om the matrix to the test workflow
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Release Notes:
New Features
Chores / Bugfixes
ACF Blocks Support
This release includes support for ACF Blocks (a premium feature of ACF Pro), while also using WPGraphQL Content Blocks v1.2.0+.
The WPGraphQL Content Blocks plugin is responsible for exposing Editor Blocks to the GraphQL Schema, and now ACF Blocks and their associated ACF Field Groups can be queried as GraphQL Types
Registering ACF Blocks
You can register ACF Blocks using code or using ACF Extended's Block Types UI.
Adding ACF Field Groups to ACF Blocks
ACF Pro allows ACF Field Groups to be assigned to ACF Blocks as a location.
After you've assigned an ACF Field Group to an ACF Block, that field group can be accessed from the block.
Example
Register the Block
Here's an example of registering an ACF Block using ACF Extended's Block Type UI. You could also register the block using code, following ACF's block registration examples.
Assign a Field Group to the Block
Then, using ACF's Field Group UI (or using JSON or PHP) you can create an ACF Field Group and associate it with an ACF Block.
See the Block in the GraphQL Schema
Next, you should be able to see the Block and the ACF Field Group associated with the block in the GraphQL Schema.
Use the Block in Content
Next, you can use the block in your content.
Query for the Block
Now you can query for EditorBlocks, and specify fields you want for your specific ACF Blocks:
ACF Options Page UI Support
ACF Pro v6.2+ introduced support for creating Options Pages using the ACF User Interface.
Now you can configure these option pages to show in the GraphQL Schema using the UI.
Here's how it works 👇🏻
Configure Options Page
When registering an Options Page via the ACF PRO v6.2+ UI, you can configure the Options Page to show in graphql, and set the GraphQL Type Name.
You will see the data in the columns on the list options page as well:
Assign a Field Group
If you assign an ACF Field Group to the Options Page:
You will be able to see that the ACF Field Group is associated with the Options Page Type
Query the Options
Then you can fill in values for the options page:
And query for the options in GraphQL:
Registering ACF Option Pages in code
You can still register options pages in PHP as you did before, adding fields
graphql_type_name
andshow_in_graphql
like shown below: