Skip to content

fix: interface conflicts with WooGraphQL v0.21.1+ #120

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 9 commits into from
May 3, 2025

Conversation

justlevine
Copy link
Member

@justlevine justlevine commented May 3, 2025

What

This PR fixes issues caused by WooGraphQL v0.21.1.

Based on #115 by @robbiebel but with CI that hasn't been autodisabled by github.

Why

#115 (comment)

How

Testing Instructions

Additional Info

Checklist:

  • My code is tested to the best of my abilities.
  • My code follows the WordPress Coding Standards.
  • My code has proper inline documentation.
  • I have added unit tests to verify the code works as intended.
  • The changes in this PR have been noted in CHANGELOG.md

@justlevine justlevine requested a review from Copilot May 3, 2025 11:50
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR addresses type conflicts in WooGraphQL v0.21.1+ by updating the changelog entry.

  • Added a changelog entry to document the fix for Product interface conflicts.
Files not reviewed (1)
  • src/Extensions/WPGraphQLWooCommerce/Type/WPObject/SeoObjects.php: Language not supported

@justlevine justlevine merged commit 3bd3ede into develop May 3, 2025
18 of 21 checks passed
@justlevine justlevine deleted the fix/woo-product-types branch May 3, 2025 11:53
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