<?php

/**
 * CRM Field Settings — tab registry.
 *
 * Each entry registers one tab on the shared CRM field-settings page.
 * Tabs only appear if their route is registered (Route::has() guard).
 *
 * To add a new module:
 *   1. Create a *FieldSettingsService
 *   2. Create a controller that returns view('core::crm-settings.crm') with $mfeConfig
 *   3. Register the module's routes
 *   4. Add one entry to this array — no Blade or JavaScript changes needed.
 *
 * Keys:
 *   route  – Named route for the tab's index action
 *   label  – Display label shown in the tab nav
 */
return [
    'tabs' => [
        ['route' => 'settings.crm.lead_fields',     'label' => 'Lead Fields'],
        ['route' => 'settings.crm.contact_fields',  'label' => 'Contact Fields'],
        ['route' => 'settings.crm.calllogs_fields', 'label' => 'Call Log Fields'],
        ['route' => 'settings.crm.ticket_fields',   'label' => 'Ticket Fields'],
    ],

    /*
     * Map each module's language namespace to its *FieldSettingsService so that
     * custom panel (section) titles saved from CRM Settings can be resolved when
     * the generic Html::section() component renders that module's panel headings
     * on create / edit / show pages.
     *
     * Only modules with editable field panels need an entry here. Modules that
     * are absent keep the previous behaviour (language-file / fallback titles).
     */
    'panel_label_services' => [
        'leads::leads'       => \Modules\Leads\Service\LeadFieldSettingsService::class,
        'contacts::contacts' => \Modules\Contacts\Service\ContactFieldSettingsService::class,
        'calllogs::calllogs' => \Modules\CallLogs\Service\CallLogFieldSettingsService::class,
        'tickets::tickets'   => \Modules\Tickets\Service\TicketFieldSettingsService::class,
    ],
];