<?php
/**
 * @package PlugixaCrm
 */

declare( strict_types = 1 );

namespace PlugixaCrm\Modules\KnowledgeBase;

if ( ! defined( 'ABSPATH' ) ) {
	exit;
}

/**
 * One switch: whether the knowledge base has a public face at all.
 *
 * IT DEFAULTS TO FALSE AND IT IS A SECOND LOCK, NOT THE ONLY ONE. An article reaches the open
 * internet only when this is on AND that article's own `public_visible` is ticked AND its status is
 * published AND it is inside its date window. Four conditions rather than one, and the per-article
 * flag is the important half — this setting can only ever narrow what those flags already permit.
 *
 * The reason there are two locks at all is what happens when somebody switches this off in a hurry:
 * a single site-wide toggle is the control an administrator reaches for when something has been
 * published that should not have been, and it has to work instantly and completely without their
 * having to find and untick the article first.
 */
final class Settings {

	public function register_hooks(): void {
		add_filter( 'plugixa_crm_settings_defaults', array( $this, 'defaults' ) );
		\PlugixaCrm\Core\Settings::add_sanitizer( 'knowledge_base', array( $this, 'sanitize' ) );
	}

	/**
	 * @param array<string, mixed> $defaults Whatever other modules registered.
	 *
	 * @return array<string, mixed>
	 */
	public function defaults( array $defaults ): array {
		return array_merge( $defaults, array( 'kb_public' => false ) );
	}

	/**
	 * @param array<string, mixed> $clean The settings cleaned so far.
	 * @param array<string, mixed> $input The raw payload.
	 *
	 * @return array<string, mixed>
	 */
	public function sanitize( array $clean, array $input ): array {
		if ( array_key_exists( 'kb_public', $input ) ) {
			$clean['kb_public'] = (bool) $input['kb_public'];
		}

		return $clean;
	}
}