<?php
/**
 * Uninstall: revoke our key and delete our webhooks if still recorded, unschedule any pending order-event,
 * product-sync and approved-product-sync actions, delete the `_cortexcommerce_paid_sent` order marker meta and the
 * `_cortexcommerce_sync_attempts` product meta, then delete every option we own (Lifecycle\Uninstaller).
 * SEO post meta (_cortexcommerce_seo_*) is merchant content and stays. So does `_cortexcommerce_generated_image_id` on
 * attachments: the images are the merchant's now, and it lets a reinstall recognise them.
 *
 * Only this build's own data goes: the production and test builds store theirs under different prefixes (Flavor).
 * When the other build is active, its classes are already loaded under the same names, so this build's autoloader
 * is not loaded (it would redeclare Composer's loader class); the other build's Uninstaller is used instead, with
 * this build's own prefixes read from its Flavor.php. Its deactivation already revoked the key and deleted the
 * webhooks (Disconnector::on_deactivate), and the other build's Options would read the other build's connection, so
 * that step is skipped.
 *
 * @package CortexCommerce
 */

defined( 'WP_UNINSTALL_PLUGIN' ) || exit;

if ( defined( 'CORTEXCOMMERCE_FILE' ) && dirname( CORTEXCOMMERCE_FILE ) !== __DIR__ ) {
	if ( class_exists( \CortexCommerce\Lifecycle\Uninstaller::class ) ) {
		$cortexcommerce_uninstaller = \CortexCommerce\Lifecycle\Uninstaller::for_flavor_file( __DIR__ . '/src/Settings/Flavor.php' );
		if ( null !== $cortexcommerce_uninstaller ) {
			$cortexcommerce_uninstaller->run( false );
		}
	}
	return;
}

require_once __DIR__ . '/vendor/autoload.php';

( new \CortexCommerce\Lifecycle\Uninstaller() )->run( true );