Hagernesh a26fa61d66 feat(warehouse): require a GRN before export cargo can be loaded onto a train ...

The export chain is: paid -> received into the warehouse -> GRN raised on arrival
-> loaded onto the allocated wagon. Receipt was already structural (the inventory
row only exists once receive() runs) and the wagon was already required, but the
GRN was merely displayed, never enforced — so cargo could be loaded and
dispatched without one.

- loadable now also requires a GRN, so the queue won't offer un-GRN'd cargo.
- loadItemsOntoTrain skips items with no GRN, so the rule holds server-side and
  a hand-made API call can't bypass it.
- Read the GRN from inv.grn_number (what receive() stamps) and fall back to the
  note only for legacy/seeded rows; it previously read the note alone, which the
  real receive path merely mirrors.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-07-17 08:01:57 +00:00

..

common

fix(train-scheduling): block dispatch when allocated cargo is not loaded

2026-07-17 08:01:57 +00:00

config

enhance train scheduling and booking management

2026-07-07 21:38:45 +00:00

contracts

changes

2026-07-15 13:29:01 +00:00

migrations

feat(last-mile): per-truck EDR arrival/exit, exit paper, bulk drawdown, departure notify

2026-07-16 09:24:22 +00:00

modules

feat(warehouse): require a GRN before export cargo can be loaded onto a train

2026-07-17 08:01:57 +00:00

scripts

add seed

2026-07-16 07:43:54 +00:00

seed

implement empty-container return service: add return quantity handling, update related DTOs, services, and UI components

2026-07-15 22:48:04 +00:00

types

Customer Truck Assignment and Portal Delivary Approval

2026-07-02 15:54:16 +03:00

app.module.ts

train

2026-07-14 13:11:38 +00:00

data-source.ts

Train scheduling API,Routes and UI

2026-06-08 16:31:28 +03:00

logger.middleware.ts

fix: logger

2026-07-03 17:21:26 +03:00

main.ts

fix fayda

2026-07-03 09:32:41 +00:00