Marshal 421e0266bc feat(train-scheduling): implement day-level booking pool ...

- Added `unplaced` method in `BookingNotifierService` to log warnings for bookings that cannot be placed on any train.
- Introduced `getAvailableDays` method in `TrainSchedulingService` to retrieve distinct days with open departures for a given route.
- Created `AvailableDaysQueryDto` for querying available days based on origin and destination yards.
- Updated `TrainSchedulingController` to expose an endpoint for available days.
- Modified frontend components to support day-level booking, allowing customers to select only a day without pinning to a specific train.
- Removed references to train schedules in booking forms and review steps, emphasizing day selection.
- Added a database migration to create an index for efficient querying of bookings by route and day.

2026-06-18 14:12:46 +00:00

..

api-common

booking flow,summtion, approval, contract, mock payemnt and integration to back office, and also add permissions

2026-06-05 10:38:31 +03:00

config

First passenger and back office portal commit

2026-05-31 13:15:44 +03:00

payment-providers

Merge pull request #201 from Tria-plc/feat/payment-microservice

2026-06-17 16:00:52 +03:00

types

feat(train-scheduling): implement day-level booking pool

2026-06-18 14:12:46 +00:00

ui-common

fixes

2026-06-16 14:27:17 +03:00