<?php
/**
 * Removes everything the plugin created.
 *
 * If a site owner uninstalls this, they should get their database back exactly as
 * it was. Leaving orphaned tables behind is how plugins earn a reputation for
 * being parasites, and it is a common reason for a one-star review.
 *
 * @package AdinavAccessibilityAuditEAA
 */

defined( 'WP_UNINSTALL_PLUGIN' ) || exit;

global $wpdb;

// The identifier is $wpdb->prefix plus a hard-coded suffix; it can never contain
// user input, and a table name cannot be bound through $wpdb->prepare().
// The schema change is the entire point of an uninstall routine: the alternative
// is leaving an orphaned table in someone's database forever.
$table = $wpdb->prefix . 'adnvaa_issues';
// phpcs:ignore PluginCheck.Security.DirectDB.UnescapedDBParameter, WordPress.DB.DirectDatabaseQuery.DirectQuery, WordPress.DB.DirectDatabaseQuery.NoCaching, WordPress.DB.PreparedSQL.NotPrepared, WordPress.DB.PreparedSQL.InterpolatedNotPrepared, WordPress.DB.DirectDatabaseQuery.SchemaChange
$wpdb->query( "DROP TABLE IF EXISTS {$table}" );

delete_option( 'adnvaa_db_version' );
delete_option( 'adnvaa_last_scan' );
delete_option( 'adnvaa_settings' );