. /** * This file contains mappings for classes that have been renamed so that they meet the requirements of the autoloader. * * Renaming isn't always the recommended approach, but can provide benefit in situations where we've already got a * close structure, OR where lots of classes get included and not necessarily used, or checked for often. * * When renaming a class delete the original class and add an entry to the db/renamedclasses.php directory for that * component. * This way we don't need to keep around old classes, instead creating aliases only when required. * One big advantage to this method is that we provide consistent debugging for renamed classes when they are used. * * @package core * @copyright 2014 Sam Hemelryk * @license http://www.gnu.org/copyleft/gpl.html GNU GPL v3 or later */ defined('MOODLE_INTERNAL') || die(); // Like other files in the db directory this file uses an array. // The old class name is the key, the new class name is the value. // The array must be called $renamedclasses. $renamedclasses = [ // Since Moodle 4.1. 'core_admin\\local\\systemreports\\task_logs' => 'core_admin\\reportbuilder\\local\\systemreports\\task_logs', 'core_admin\\local\\entities\\task_log' => 'core_admin\\reportbuilder\\local\\entities\\task_log', 'core_course\\local\\entities\\course_category' => 'core_course\\reportbuilder\\local\\entities\\course_category', 'core_cohort\\local\\entities\\cohort' => 'core_cohort\\reportbuilder\\local\\entities\\cohort', 'core_cohort\\local\\entities\\cohort_member' => 'core_cohort\\reportbuilder\\local\\entities\\cohort_member', 'core_block\\local\\views\\secondary' => 'core_block\\navigation\\views\\secondary', // Since Moodle 4.2. 'Box\\Spout' => 'OpenSpout', // Since Moodle 4.3. 'core_question\\bank\\search\\condition' => 'core_question\\local\\bank\\condition', 'core_question\\bank\\search\\category_condition' => 'qbank_managecategories\\category_condition', 'core_question\\bank\\search\\hidden_condition' => 'qbank_deletequestion\\hidden_condition', ];