ncoronel
5197862a62
- Added `ticket_generation_policy` column to `catalog_items` table to manage ticket generation strategies. - Created `ticket_validity_times` table to allow multiple validity times per ticket. - Introduced `validity_time_id` column in `event_dates` table to associate event dates with validity times. - Established `ticket_validity_groups` and `ticket_validity_group_times` tables to group validity times for tickets. - Updated seeder to set default ticket generation policy for specific tenant. - Enhanced tests to cover new functionality, including ticket generation based on event dates and validity times. - Refactored ticket validity checks to accommodate multiple validity times in a group.
36 lines
1.0 KiB
PHP
36 lines
1.0 KiB
PHP
<?php
|
|
|
|
namespace App\Domains\Forms\Services;
|
|
|
|
use App\Domains\Catalog\Models\Attribute;
|
|
use App\Domains\Catalog\Models\AttributeOption;
|
|
use App\Domains\Event\Models\EventDate;
|
|
use App\Domains\Tenant\Models\Tenant;
|
|
use Illuminate\Database\Eloquent\Collection;
|
|
|
|
class FoodFormService
|
|
{
|
|
/**
|
|
* @return array{
|
|
* event_dates: Collection<int, EventDate>,
|
|
* schedules: Collection<int, AttributeOption>,
|
|
* services: Collection<int, AttributeOption>
|
|
* }
|
|
*/
|
|
public function get(Tenant $tenant): array
|
|
{
|
|
$attributes = Attribute::query()
|
|
->where('tenant_codigo', $tenant->codigo)
|
|
->whereIn('codigo', ['horario', 'servicio'])
|
|
->with('options')
|
|
->get()
|
|
->keyBy('codigo');
|
|
|
|
return [
|
|
'event_dates' => $tenant->eventDates()->with('validityTime')->get(),
|
|
'schedules' => $attributes->get('horario')?->options ?? new Collection,
|
|
'services' => $attributes->get('servicio')?->options ?? new Collection,
|
|
];
|
|
}
|
|
}
|