feat: add Appsero telemetry tracking to WPGraphQL IDE#3765
Merged
Conversation
Add opt-in telemetry via Appsero SDK to help troubleshoot issues and improve the plugin. No data is collected without explicit user consent. - Add appsero/client 2.0.6 as a Composer dependency - Add init_appsero_telemetry() with defensive error handling (matching the pattern used in the core WPGraphQL plugin) - Load Composer autoloader in the main plugin file - Remove /vendor from .distignore so the dependency ships in releases - Add Privacy Policy sections to readme.txt and README.md
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #3765 +/- ##
=======================================
Coverage 83.3% 83.3%
Complexity 5193 5193
=======================================
Files 286 286
Lines 22555 22555
=======================================
Hits 18799 18799
Misses 3756 3756
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
Add wp-env:cli, lint:php, lint:php:fix, and lint:php:stan scripts matching the pattern used in wp-graphql and wp-graphql-acf for consistent local development experience across the monorepo.
The PHPSTAN constant guard causes PHPStan to exit early, so the varTag.type error is never reported and the ignore annotation is flagged as unnecessary.
Define the PHPSTAN constant so the defined('PHPSTAN') guard in
init_appsero_telemetry() works correctly during static analysis,
matching the pattern used in the core wp-graphql plugin.
- Upgrade phpstan/phpstan to ~2.1.2, szepeviktor/phpstan-wordpress to ^2.0.1, add phpstan-deprecation-rules ^2.0.1 - Align phpstan.neon.dist with core: remove bootstrapped main file, remove deprecated 1.x-only config options, add phpVersion bounds, add ignoreErrors for build assets - Restore @var and @PHPStan-Ignore annotations on Appsero insights() call to fix type resolution (matching core pattern)
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
appsero/clientv2.0.6) as a Composer dependency to the WPGraphQL IDE plugin for opt-in telemetry trackinginit_appsero_telemetry()initialization inwpgraphql-ide.php, following the same defensive patterns as the core WPGraphQL plugin (class_exists guard, PHPSTAN guard, try/catch, error logging)/vendorfrom.distignoreso the Appsero dependency ships in plugin releasesreadme.txt(with FAQ entry) andREADME.mdto comply with WordPress.org guidelinesDetails
The Appsero project ID for WPGraphQL IDE is
e90103d6-2c09-4152-96e0-eb7d0d3b5c74.No data is collected without explicit user consent via an admin notice. The integration mirrors the approach already used in the core
wp-graphqlplugin.Files changed
composer.jsonappsero/client: 2.0.6torequirewpgraphql-ide.phpinit_appsero_telemetry().distignore/vendorexclusionreadme.txtREADME.mdCI / Deploy
No workflow changes needed. The existing
integration-tests-reusable.ymlalready runscomposer installper-plugin, andrelease-please.ymlrunscomposer install --no-devbefore building the deployment artifact. Vendor exclusions in.eslintignore,phpcs.xml.dist, andphpstan.neon.distare already in place.Test plan
composer installsucceeds inplugins/wp-graphql-ide/