Feat/#39 options pages support #41
Merged
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 adds support for ACF Options Pages to be exposed to the WPGraphQL Schema and queried for.
What currently open issues does this close or contribute?
closes #39
Any other comments?
ACF Options pages are now exposed to the GraphQL Schema.
I can register an ACF Options Page like so:
I can then assign an ACF Field Group to the Options Page:
I will see that the GraphQL Settings for the field group map the Field Group to the GraphQL Type that represents the options page:
I can update values in the Options Page:
And then I can query the options page and the associated Field Group(s)
Bonus: WPGraphQL Smart Cache Support
This also works with WPGraphQL Smart Cache, so my queries for ACF Options can be cached and when updating an options page, queries for that options page will be purged, so we can have fresh data always!
We can see in the WPGraphQL Smart Cache Logs that purge events are happening when I update ACF Options: