Skip to content
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

Make sure oembed field is also formatted when part of a flexible_content field #126

Merged
merged 1 commit into from
Nov 21, 2023

Conversation

kpoelhekke
Copy link
Contributor

@kpoelhekke kpoelhekke commented Nov 17, 2023

What does this implement/fix? Explain your changes.

This change makes sure that fields that are part of a flexible_content field are also formatted. Currently this is not the case for the oembed field for example.

Does this close any currently open issues?

No, but relates to #106

Any relevant logs, error output, GraphiQL screenshots, etc?

Before

image

After

image

Any other comments?

This is a breaking change.

@kpoelhekke kpoelhekke changed the title - make sure oembed field is also formatted when part of a flexible_content field Make sure oembed field is also formatted when part of a flexible_content field Nov 17, 2023
@jasonbahl
Copy link
Contributor

@kpoelhekke thanks! I'm running the tests now to confirm. Unfortunately they will fail when a PR is opened from outside the repo because some repo secrets are needed to test against ACF PRO, but I'm checking now

@jasonbahl
Copy link
Contributor

jasonbahl commented Nov 21, 2023

@kpoelhekke I've confirmed existing tests pass. We don't have a great setup for testing individual fields as sub-fields of repeaters or flex fields yet, so I'm going to open up an issue (see: #127) to better support testing fields within repeaters/flex fields so we can stay on top of these cases going forward.

@jasonbahl jasonbahl merged commit 24bd4cd into wp-graphql:main Nov 21, 2023
13 of 23 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants