Skip to content

Conversation

jasonbahl
Copy link
Contributor

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

  • #156: feat: Use published ACF values in resolvers for fields associated with posts that use the block editor, since the Block Editor has a bug preventing meta from being saved for previews. Adds a debug message if ACF fields are queried for with "asPreview" on post(s) that use the block editor.

Chores / Bugfixes

  • #156: fix: ACF Fields not resolving when querying "asPreview"
  • #155: fix: "show_in_graphql" setting not being respected when turned "off"
  • #152: fix: performance issues with mapping ACF Field Groups to the Schema
  • #148: fix: bug when querying taxonomy field on blocks
  • #146: chore: update phpcs to match core WPGraphQL

Create sync-develop-with-main.yml
…ore-wpgraphql

Chore/update phpcs to match core wpgraphql
- Add test case for querying taxonomy field on ACF Block when only 1 category is stored
… 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"
@jasonbahl jasonbahl added the release Pull request intended for a release label Jan 23, 2024
@jasonbahl jasonbahl requested a review from josephfusco January 23, 2024 22:53
@jasonbahl jasonbahl self-assigned this Jan 23, 2024
@coveralls
Copy link

coveralls commented Jan 23, 2024

Pull Request Test Coverage Report for Build 0281ea6676a395debbdd3ec945f1b141797c1bf8-PR-160

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.08%) to 62.446%

Totals Coverage Status
Change from base Build 114a2fec7ee8854c7a3d953bbc9884becaefe385: 0.08%
Covered Lines: 2032
Relevant Lines: 3254

💛 - 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
@jasonbahl jasonbahl merged commit 122d9ed into main Jan 24, 2024
@jasonbahl jasonbahl deleted the release/v2.1.0 branch January 24, 2024 20:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release Pull request intended for a release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants