-
Notifications
You must be signed in to change notification settings - Fork 15
release: v2.1.0 #160
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
Merged
Merged
release: v2.1.0 #160
Conversation
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
Create sync-develop-with-main.yml
…ore-wpgraphql Chore/update phpcs to match core wpgraphql
…tem is selected instead of multiple items
- Add test case for querying taxonomy field on ACF Block when only 1 category is stored
…ocks fix: #133 taxonomy field on blocks
… not try and dynamically determine location rules at Schema Generation time.
…r field groups that have graphql_types defined, but still support field groups that don't have graphql_types defined.
… Field Group Location rules to reduce redundancy - remove unneeded LocationRules - update OptionsPageTest to clear the schema during setUp
…phQL\Utils\Utils - normalize location rules to be mapped with strolower
…gistered to the Schema - Use the registered field names and keys to determine wether or not to resolve the field from the post itself (if revision meta is supported) or the parent (if it's not).
…with-preview fix: acf fields not resolving with preview
fix: "show in graphql" setting on fields not respecting being turned "off"
…hql-acf into fix/performance-issues
fix: performance issues for mapping field groups to the Schema
Update README.md
Pull Request Test Coverage Report for Build 0281ea6676a395debbdd3ec945f1b141797c1bf8-PR-160
💛 - Coveralls |
…ly triggered. That will allow the `wpgraphql/acf/match_location_rule` action to fire and the other rules can be compensated via that action
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
Upgrade Notice
While fixing some performance issues we had to adjust the fallback logic for mapping ACF Field Groups to the Schema if they do not have "graphql_types" defined.
ACF Field Groups that did not have "graphql_types" defined AND were assigned to Location Rules based on "post_status", "post_format", "post_category" or "post_taxonomy" might not show in the Schema until their "graphql_types" are explicitly defined.
New Features
Chores / Bugfixes