Skip to content

Conversation

@theodesp
Copy link
Member

@theodesp theodesp commented Jul 16, 2025

Description

This PR adds the basic plugin skeleton for wpgraphql-debug-extensions. This includes:

  • Namespace: The primary namespace is WPGraphQL\Debug.

  • Text Domain: The plugin's text domain has been set to wpgraphql-debug-extensions.

  • README: The README.md file has been added to describe the plugin's purpose as a base for debug extensions, clarifying that it's currently a skeleton with no functionality beyond the core setup.

  • Complexity Metric: Calculates a "complexity score" for each GraphQL query based on the number of fields, fragments, and inline fragments selected. Provides contextual notes in the debugExtensions output, categorizing queries as "Low," "Moderate," "High," or "Very High" complexity.

Related Issue

#337

Dependant PRs

Type of Change

  • ✅ Bug fix (non-breaking change which fixes an issue)
  • ✨ New feature (non-breaking change which adds functionality)
  • 💥 Breaking change (fix or feature that would cause existing functionality to change)
  • 🧹 Code refactoring (no functional changes)
  • 📄 Example update (no functional changes)
  • 📝 Documentation update
  • 🔍 Performance improvement
  • 🧪 Test update

How Has This Been Tested?

Screenshots

N/A - This PR does not introduce any UI/UX changes.

Checklist

  • I have read the CONTRIBUTING document
  • My code follows the project's coding standards
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation (if applicable)
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works (if applicable)
  • Any dependent changes have been highlighted, merged or published

@theodesp theodesp requested a review from a team as a code owner July 16, 2025 12:41
@changeset-bot
Copy link

changeset-bot bot commented Jul 16, 2025

⚠️ No Changeset found

Latest commit: 768ec32

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@theodesp theodesp requested a review from josephfusco July 16, 2025 12:41
@github-actions
Copy link

github-actions bot commented Jul 16, 2025

ℹ️ Download the latest wpgraphql-debug-extensions plugin zip from this PR
(See the 'Artifacts' section at the bottom)

@github-actions
Copy link

github-actions bot commented Jul 21, 2025

ℹ️ Download the latest wp-graphql-webhooks plugin zip from this PR
(See the 'Artifacts' section at the bottom)

colinmurphy
colinmurphy previously approved these changes Jul 21, 2025
Copy link
Member

@colinmurphy colinmurphy left a comment

Choose a reason for hiding this comment

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

@theodesp

This looks good to me. Some minor suggestions in the PR ❤️ 🚀

Co-authored-by: Colin Murphy <colinmurphy@users.noreply.github.com>
Copy link
Member

@colinmurphy colinmurphy left a comment

Choose a reason for hiding this comment

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

LGTM 🚀 🚀 🚀

@theodesp theodesp added this pull request to the merge queue Jul 28, 2025
Merged via the queue into main with commit e8fb779 Jul 28, 2025
9 checks passed
@theodesp theodesp deleted the wpgraphql-debug-extensions-plugin-start branch July 28, 2025 09:07
@github-project-automation github-project-automation bot moved this from 🆕 Backlog to ✅ Closed in Headless OSS Jul 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: ✅ Closed

Development

Successfully merging this pull request may close these issues.

3 participants