<?php
/**
 * F14 — who may use Oorank.
 *
 * Every screen and route was `manage_options`, which is administrator-only.
 * That excludes editors and authors — exactly the people the author-entity and
 * answer-ready work is built for — and makes the plugin unusable on the
 * multi-author and agency sites it is aimed at.
 *
 * A dedicated capability rather than a role check: `oorank_manage` can be
 * granted to a role from the settings screen, granted to one user by another
 * plugin, or granted by a membership plugin that knows nothing about Oorank.
 * Administrators keep access through `manage_options` regardless, so a
 * misconfigured role list can never lock the owner out of the screen that
 * fixes it.
 *
 * @package Oorank
 */

defined( 'ABSPATH' ) || exit;

/**
 * Capability management.
 */
class Oorank_Roles {

	/**
	 * The capability Oorank's screens and routes require.
	 */
	const CAP = 'oorank_manage';

	/**
	 * Roles that always hold the capability, whatever the setting says.
	 */
	const ALWAYS = array( 'administrator' );

	/**
	 * Whether the current user may manage Oorank.
	 *
	 * @return bool
	 */
	public static function can() {
		return current_user_can( self::CAP ) || current_user_can( 'manage_options' );
	}

	/**
	 * The capability string to hand WordPress APIs that take one.
	 *
	 * `add_menu_page()` and `register_rest_route()` want a capability, not a
	 * callback, so they get the custom one — administrators hold it because
	 * sync() grants it to them and never takes it away.
	 *
	 * @return string
	 */
	public static function cap() {
		/**
		 * Filter the capability Oorank requires.
		 *
		 * @param string $cap Capability name.
		 */
		return apply_filters( 'oorank_capability', self::CAP );
	}

	/**
	 * Roles that should hold the capability, per the saved setting.
	 *
	 * @param Oorank_Settings $settings Settings store.
	 * @return string[]
	 */
	public static function granted( Oorank_Settings $settings ) {
		$all   = $settings->get();
		$roles = isset( $all['roles']['manage'] ) ? (array) $all['roles']['manage'] : array();

		return array_values( array_unique( array_merge( self::ALWAYS, array_map( 'sanitize_key', $roles ) ) ) );
	}

	/**
	 * Grant the capability to the chosen roles and take it from the rest.
	 *
	 * @param Oorank_Settings $settings Settings store.
	 */
	public static function sync( Oorank_Settings $settings ) {
		$granted = self::granted( $settings );

		foreach ( self::assignable() as $slug => $label ) {
			unset( $label );

			$role = get_role( $slug );
			if ( ! $role ) {
				continue;
			}

			if ( in_array( $slug, $granted, true ) ) {
				$role->add_cap( self::CAP );
			} else {
				$role->remove_cap( self::CAP );
			}
		}
	}

	/**
	 * Roles the setting can hand the capability to.
	 *
	 * Only roles that can already edit something: giving Oorank to a
	 * subscriber would be granting a content tool to an account that has no
	 * content, and the audit's fix links all lead to the editor.
	 *
	 * @return array<string, string> slug => display name.
	 */
	public static function assignable() {
		$roles = array();

		foreach ( wp_roles()->roles as $slug => $role ) {
			$caps = isset( $role['capabilities'] ) ? $role['capabilities'] : array();
			if ( empty( $caps['edit_posts'] ) && empty( $caps['manage_options'] ) ) {
				continue;
			}
			$roles[ $slug ] = translate_user_role( $role['name'] );
		}

		return $roles;
	}
}